Mobile control application for managing an information management system

ABSTRACT

A control application facilitates interactions with, and configurations of, the information management system that manages one or more client computing devices of an information management system. The control application may be implemented using a variety of modules that allow a user to interact with the information management system services in various ways. Using the control application, a user may view a backup status of the information management system, and view the backup status of specific client computing devices that are managed by the information management system. The user may also search for various entities and/or objects within the information management system using the control application. In addition, a user may view the status of one or more backup jobs configured within the information management system, as well as backup plans that have been established for one or more of the client computing devices.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of priority to U.S. patent application Ser. No. 17/488,156, titled “MOBILE STORAGE MANAGER CONTROL APPLICATION FOR MANAGING A STORAGE MANAGER OF AN INFORMATION MANAGEMENT SYSTEM” and filed Sep. 28, 2021, which claims the benefit of priority to U.S. Pat. App. No. 63/236,147, titled “MOBILE STORAGE MANAGER CONTROL APPLICATION FOR MANAGING A STORAGE MANAGER OF AN INFORMATION MANAGEMENT SYSTEM” and filed Aug. 23, 2021, the disclosure of which is hereby incorporated by reference in its entirety.

Any and all applications, if any, for which a foreign or domestic priority claim is identified in the Application Data Sheet of the present application are hereby incorporated by reference in their entireties under 37 CFR 1.57.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document and/or the patent disclosure as it appears in the United States Patent and Trademark Office patent file and/or records, but otherwise reserves all copyrights whatsoever.

BACKGROUND

Businesses recognize the commercial value of their data and seek reliable, cost-effective ways to protect the information stored on their computer networks while minimizing impact on productivity. A company might back up critical computing systems such as databases, file servers, web servers, virtual machines, and so on as part of a daily, weekly, or monthly maintenance schedule. The company may similarly protect computing systems used by its employees, such as those used by an accounting department, marketing department, engineering department, and so forth. Given the rapidly expanding volume of data under management, companies also continue to seek innovative techniques for managing data growth, for example by migrating data to lower-cost storage over time, reducing redundant data, pruning lower priority data, etc. Enterprises also increasingly view their stored data as a valuable asset and look for solutions that leverage their data. For instance, data analysis capabilities, information management, improved data presentation and access features, and the like, are in increasing demand.

In protecting the computing systems used by employees, the company may use a comprehensive backup system for backing up one or more of the computing systems. Often, the centralized system may require an administrator or operator to instruct the comprehensive backup system how to perform its duties and/or to configure the comprehensive backup system to operate according to the demands and/or needs of the company. In some instances, the comprehensive backup system may allow the administrator or operator to configure or operate it using a graphical user interface, such as an application or program designed to interact with the comprehensive backup system. However, the graphical user interface may be flawed and/or incomplete, and may not include access to many of the features that the comprehensive backup system is able to use and/or provide. Furthermore, the graphical user interface may be designed to operate on a desktop or other non-mobile platform, which can lead to problems maintaining or configuring the comprehensive backup system when the administrator and/or operator is on the move or only has access to a mobile computing device.

SUMMARY

To address these and other deficiencies, this disclosure describes an information management system that uses a mobile control application for controlling and/or configuring a storage manager of the information management system. At times, this disclosure may refer to the mobile control application as the “storage manager control application” or the “information management control application.” As discussed below, a storage manager may be a centralized storage and/or information manager that is configured to perform certain control functions and also to store certain critical information about the information management system. The storage manager control application is configured and/or programmed to provide access to the storage manager and/or to implement various features that the storage manager provides to the information management system.

Unlike a traditional desktop or programmatic application, the storage manager control application is configured to operate on a mobile computing device and to communicate with the storage manager using the mobile computing device. The storage manager control application may implement various modules that allow the administrator or operator of the information management system to interact with the storage manager and to instruct the storage manager to perform various operations and/or functions.

One module that the storage manager control application may implement is a system status module, where the system status module instructs the storage manager to provide system status information about the information management system. The system status module may display a graphical user interface on the mobile computing device that displays the system status information, which may include a number of computing devices that are backed up and/or protected by the information management system, usage statistics for one or more secondary storage devices within the information management system, backup statistics for one or more client computing devices within the information management system, and other such system status information. In addition, system status module may allow the user of the storage manager control application to inspect specific client computing devices and review the backup status for selected one or more client computing devices.

Another module that the storage manager control application may implement is a client status module, where the client status module is configured to provide client-specific information for one or more client computing devices of the information management system. The client status module may communicate with the storage manager to obtain real-time and/or near real-time client information about one or more client computing devices that are managed by the storage manager within the information management system. The client information may include such information as a time and/or date when the client computing device was last backed up, whether a backup job for a corresponding client computing device was successful, one or more reasons explaining and/or detailing why a backup job did not complete for a corresponding client computing device, and other such client information. Furthermore, the client status module may be configured to permit and/or allow a user of the storage manager control application to perform diagnostics on selected client computing devices, which can help the user identify and/or determine potential solutions to any problems that the selected client computing devices may be experiencing (e.g., in the event of a backup job failure).

The storage manager control application may also implement a backup jobs module that allows the user of the storage manager control application to explore and/or inspect one or more backup jobs scheduled with the storage manager. As the storage manager is configured to manager the client computing devices of the information management system, the storage manager may also manage one or more backup jobs for the client computing devices. As discussed in detail below, a backup job is generally considered a logical grouping of secondary copy operations governed by a rule set and being initiated at a point in time. The storage manager may be responsible for initiating one or more backup jobs for various client computing devices, and some of those backup jobs may succeed and some of those backup jobs may not. Using the backup jobs module of the storage manager control application, the user can inspect and/or examine one or more of the backup jobs at an individualistic or granular level. This allows the user to identify which particular backup jobs have failed, which client computing devices may be have been impacted by the failure, and to formulate potential solutions for addressing the failed backup jobs. All of these features of the backup jobs module ensure that the client computing devices are sufficiently protected and that data integrity and availability is maintained throughout the information management system.

Yet another module that the storage manager control application may implemented is a search module, which allows the user to search for various devices and/or objects across the information management system. The search module may provide a graphical user interface that allows the user to search for the different types of devices and/or objects within the information management system including, one or more client computing devices, logical groups of client computing devices, backup plans, media agents, file servers, and other such devices and/or objects. In response to a search query, the search module may display one or more devices and/or objects that match the provided search query. Using the graphical user interface, a user may perform one or more operations on the matching devices and/or objects, where the search module displays available operations to perform based on a selected object type (e.g., a selected client computing device, a selected server, a selected backup plan, a selected user, etc.). In this way, the search module allows a user to perform various operations on devices and/or objects within the information management system without having to directly access the selected device and/or object.

In addition, the storage manager control application may include a plan module that allows a user to view one or more backup plans that are managed by the storage manager. Using the plan module, the user of the storage manager control application may view which client computing devices are protected for a corresponding backup plan, and may further display a recovery point objective associated with the corresponding backup plan. By using the plan module, a user of the storage manager control application can better understand the backup landscape for the information management system and make adjustments to the storage manager as needed or desired.

Furthermore, the storage manager control application may include an account module that allows the user of the storage manager control application to perform administrative operations on the storage manager control application and to view details about the user account associated with the user. The account module may allow the user to check for and/or obtain software updates for the storage manager control application and, when requested, to send log files and/or log file details to the storage manager. The log files and/or log file details may be requested by an administrator and/or operator of the information management system, and may be used by him or her in the event that the storage manager control application encounters an error or exhibits unwanted behavior.

The storage manager control application represents an advancement in storage manager administration because it allows a user to remotely administer the storage manager using a mobile computing device rather than a desktop computing device. As a mobile computing device has limited resources, both in computing power and available display area, the storage manager control application is uniquely positioned to provide mobile administration of a storage manager in an information management system when the administrator and/or operator cannot access a traditional desktop environment. As the desktop administration of the storage manager may provide an overwhelming amount of information about the information management system, the storage manager control application streamlines this process and provides the information that would be most relevant to the mobile user. Where the desktop environment migrated to a mobile computing device would be cumbersome, unwieldy, and provide too many details that can be displayed on the limited display of a mobile computing device, the disclosed storage manager control application is optimized to operate within the mobile computing space and provide the administrator and/or operator with the tools he or she needs to successfully manage the information management system.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is a block diagram illustrating an exemplary information management system.

FIG. 1B is a detailed view of a primary storage device, a secondary storage device, and some examples of primary data and a secondary copy of the primary data.

FIG. 1C is a block diagram of an exemplary information management system including a storage manager, one or more data agents, and one or more media agents.

FIG. 1D is a block diagram illustrating a scalable information management system.

FIG. 1E illustrates certain secondary copy operations according to an exemplary storage policy.

FIGS. 1F-1H are block diagrams illustrating suitable data structures that may be employed by the information management system.

FIG. 2A illustrates a system and technique for synchronizing primary data to a destination such as a failover site using a secondary copy.

FIG. 2B illustrates an information management system architecture incorporating use of a network file system (NFS) protocol for communicating between the primary and secondary storage subsystems.

FIG. 2C is a block diagram of an example of a highly scalable managed data pool architecture.

FIG. 3 illustrates an information management system that can be managed via a storage manager control application operating on a mobile computing device, in accordance with an example embodiment.

FIG. 4 is a block diagram of a mobile computing device from FIG. 3 , where the mobile computing device instantiates a storage manager control application having various different modules for interacting with the storage manager of FIG. 3 , in accordance with an example embodiment.

FIG. 5 illustrates a graphical user interface provided by a login module of a storage manager control application, where the graphical user interface facilitates access to the information management system, in accordance with an example embodiment.

FIGS. 6A-6B illustrate a continuous graphical user interface generated by a system status module of a storage manager control application, where the system status module provides system status information about the information management system of FIG. 3 , in accordance with an example embodiment.

FIG. 7 illustrates a graphical user interface generated by a client status module of a storage manager control application, where the client status module provides client status information for one or more unprotected clients of the information management system of FIG. 3 , in accordance with an example embodiment.

FIGS. 8A-8D illustrate a graphical user interface generated by a jobs module of a storage manager control application, where the jobs module provides access to one or more backup jobs of the information management system of FIG. 3 , in accordance with an example embodiment.

FIGS. 9A-9E illustrate a graphical user interface generated by a search module of a storage manager control application, where the search module allows a user to search for various entities within the information management system of FIG. 3 , in accordance with an example embodiment.

FIG. 10 illustrates a graphical user interface generated by a plan module of a storage manager control application, where the plan module allows a user to review backup plans configured within the information management system of FIG. 3 , in accordance with an example embodiment.

FIG. 11 illustrates a graphical user interface generated by an account module of a storage manager control application, where the account module allows a user to interact with various account settings and configurations of a user account, in accordance with an example embodiment.

DETAILED DESCRIPTION

Detailed descriptions and examples of systems and methods according to one or more illustrative embodiments may be found in the section titled “Mobile Storage Manager Control Application,” as well as in the section titled Example Embodiments, and also in FIGS. 3-11 herein. Furthermore, components and functionality for the disclosed recovery manager may be configured and/or incorporated into information management systems such as those described herein in FIGS. 1A-1H and 2A-2C.

Various embodiments described herein are intimately tied to, enabled by, and would not exist except for, computer technology. For example, the transference of backup jobs from the storage manager to the recovery manager described herein, in reference to various embodiments, cannot reasonably be performed by humans alone, without the computer technology upon which they are implemented.

Information Management System Overview

With the increasing importance of protecting and leveraging data, organizations simply cannot risk losing critical data. Moreover, runaway data growth and other modern realities make protecting and managing data increasingly difficult. There is therefore a need for efficient, powerful, and user-friendly solutions for protecting and managing data and for smart and efficient management of data storage. Depending on the size of the organization, there may be many data production sources which are under the purview of tens, hundreds, or even thousands of individuals. In the past, individuals were sometimes responsible for managing and protecting their own data, and a patchwork of hardware and software point solutions may have been used in any given organization. These solutions were often provided by different vendors and had limited or no interoperability. Certain embodiments described herein address these and other shortcomings of prior approaches by implementing scalable, unified, organization-wide information management, including data storage management.

FIG. 1A shows one such information management system 100 (or “system 100”), which generally includes combinations of hardware and software configured to protect and manage data and metadata that are generated and used by computing devices in system 100. System 100 may be referred to in some embodiments as a “storage management system” or a “data storage management system.” System 100 performs information management operations, some of which may be referred to as “storage operations” or “data storage operations,” to protect and manage the data residing in and/or managed by system 100. The organization that employs system 100 may be a corporation or other business entity, non-profit organization, educational institution, household, governmental agency, or the like.

Generally, the systems and associated components described herein may be compatible with and/or provide some or all of the functionality of the systems and corresponding components described in one or more of the following U.S. patents/publications and patent applications assigned to Commvault Systems, Inc., each of which is hereby incorporated by reference in its entirety herein:

-   -   U.S. Pat. No. 7,035,880, entitled “Modular Backup and Retrieval         System Used in Conjunction With a Storage Area Network”;     -   U.S. Pat. No. 7,107,298, entitled “System And Method For         Archiving Objects In An Information Store”;     -   U.S. Pat. No. 7,246,207, entitled “System and Method for         Dynamically Performing Storage Operations in a Computer         Network”;     -   U.S. Pat. No. 7,315,923, entitled “System And Method For         Combining Data Streams In Pipelined Storage Operations In A         Storage Network”;     -   U.S. Pat. No. 7,343,453, entitled “Hierarchical Systems and         Methods for Providing a Unified View of Storage Information”;     -   U.S. Pat. No. 7,395,282, entitled “Hierarchical Backup and         Retrieval System”;     -   U.S. Pat. No. 7,529,782, entitled “System and Methods for         Performing a Snapshot and for Restoring Data”;     -   U.S. Pat. No. 7,617,262, entitled “System and Methods for         Monitoring Application Data in a Data Replication System”;     -   U.S. Pat. No. 7,734,669, entitled “Managing Copies Of Data”;     -   U.S. Pat. No. 7,747,579, entitled “Metabase for Facilitating         Data Classification”;     -   U.S. Pat. No. 8,156,086, entitled “Systems And Methods For         Stored Data Verification”;     -   U.S. Pat. No. 8,170,995, entitled “Method and System for Offline         Indexing of Content and Classifying Stored Data”;     -   U.S. Pat. No. 8,230,195, entitled “System And Method For         Performing Auxiliary Storage Operations”;     -   U.S. Pat. No. 8,285,681, entitled “Data Object Store and Server         for a Cloud Storage Environment, Including Data Deduplication         and Data Management Across Multiple Cloud Storage Sites”;     -   U.S. Pat. No. 8,307,177, entitled “Systems And Methods For         Management Of Virtualization Data”;     -   U.S. Pat. No. 8,364,652, entitled “Content-Aligned, Block-Based         Deduplication”;     -   U.S. Pat. No. 8,578,120, entitled “Block-Level Single         Instancing”;     -   U.S. Pat. No. 8,954,446, entitled “Client-Side Repository in a         Networked Deduplicated Storage System”;     -   U.S. Pat. No. 9,020,900, entitled “Distributed Deduplicated         Storage System”;     -   U.S. Pat. No. 9,098,495, entitled “Application-Aware and Remote         Single Instance Data Management”;     -   U.S. Pat. No. 9,239,687, entitled “Systems and Methods for         Retaining and Using Data Block Signatures in Data Protection         Operations”;     -   U.S. Pat. Pub. No. 2006/0224846, entitled “System and Method to         Support Single Instance Storage Operations” (now abandoned);     -   U.S. Pat. Pub. No. 2014/0201170, entitled “High Availability         Distributed Deduplicated Storage System”, now U.S. Pat. No.         9,633,033;     -   U.S. Pat. Pub. No. 2016/0041880 A1, entitled “Efficient         Application Recovery in an Information Management System Based         on a Pseudo-Storage-Device Driver”, now U.S. Pat. No. 9,852,026;     -   U.S. patent application Ser. No. 14/721,971, entitled         “Replication Using Deduplicated COMMV.252A), published as U.S.         Pat. Pub. No. 2016/0350391;     -   U.S. patent application Ser. No. 14/805,615, entitled “Browse         and Restore for Block-Level Backups” (applicant matter no.         100.434.US1.120; attorney docket no. 060692-8141.US00), now U.S.         Pat. No. 9,766,825.     -   U.S. Provisional Patent Application No. 62/265,339 entitled         “Live Synchronization and Management of Virtual Machines across         Computing and Virtualization Platforms and Using Live         Synchronization to Support Disaster Recovery” (applicant docket         no. 100.487.USP1.160; attorney docket no. COMMV.277PR), to which         U.S. patent application Ser. No. 15/365,756 claims priority (now         U.S. Pat. No. 10,228,962);     -   U.S. Provisional Patent Application No. 62/273,286 entitled         “Redundant and Robust Distributed Deduplication Data Storage         System” (applicant docket no. 100.489.USP1.135; attorney docket         no. COMMV.279PR), to which U.S. patent application Ser. Nos.         15/299,254 (now U.S. Pat. No. 10,310,953), Ser. No. 15/299,281         (published as U.S. Pat Pub. 2017-0192868), Ser. No. 15/299,291         (now U.S. Pat. No. 10,138,729), Ser. No. 15/299,298 (now U.S.         Pat. No. 10,592,357), Ser. No. 15/299,299 (published as U.S.         Pat. Pub. US 2017-0193003), and Ser. No. 15/299,280 (now U.S.         Pat. No. 10,061,663) all claim priority;     -   U.S. Provisional Patent Application No. 62/294,920, entitled         “Data Protection Operations Based on Network Path Information”         (applicant docket no. 100.497.USP1.105; attorney docket no.         COMMV.283PR), to which U.S. patent application Ser. No.         15/283,033 claims priority (published as U.S. Pat. Pub. No.         2017/0235647 (now abandoned));     -   U.S. Provisional Patent Application No. 62/297,057, entitled         “Data Restoration Operations Based on Network Path Information”         (applicant docket no. 100.498.USP1.105; attorney docket no.         COMMV.284PR), to which U.S. patent application Ser. No.         15/286,403 claims priority (published as U.S. Pat. Pub. No.         2017/0242871); and     -   U.S. Provisional Patent Application No. 62/387,384, entitled         “Application-Level Live Synchronization Across Computing         Platforms Including Synchronizing Co-Resident Applications To         Disparate Standby Destinations And Selectively Synchronizing         Some Applications And Not Others” (applicant docket no.         100.500.USP1.105; attorney docket no. COMMV.286PR), to which         U.S. patent application Ser. No. 15/369,676 claims priority (now         U.S. Pat. No. 10,387,266).

System 100 includes computing devices and computing technologies. For instance, system 100 can include one or more client computing devices 102 and secondary storage computing devices 106, as well as storage manager 140 or a host computing device for it. Computing devices can include, without limitation, one or more: workstations, personal computers, desktop computers, or other types of generally fixed computing systems such as mainframe computers, servers, and minicomputers. Other computing devices can include mobile or portable computing devices, such as one or more laptops, tablet computers, personal data assistants, mobile phones (such as smartphones), and other mobile or portable computing devices such as embedded computers, set top boxes, vehicle-mounted devices, wearable computers, etc. Servers can include mail servers, file servers, database servers, virtual machine servers, and web servers. Any given computing device comprises one or more processors (e.g., CPU and/or single-core or multi-core processors), as well as corresponding non-transitory computer memory (e.g., random-access memory (RAM)) for storing computer programs which are to be executed by the one or more processors. Other computer memory for mass storage of data may be packaged/configured with the computing device (e.g., an internal hard disk) and/or may be external and accessible by the computing device (e.g., network-attached storage, a storage array, etc.). In some cases, a computing device includes cloud computing resources, which may be implemented as virtual machines. For instance, one or more virtual machines may be provided to the organization by a third-party cloud service vendor.

In some embodiments, computing devices can include one or more virtual machine(s) running on a physical host computing device (or “host machine”) operated by the organization. As one example, the organization may use one virtual machine as a database server and another virtual machine as a mail server, both virtual machines operating on the same host machine. A Virtual machine (“VM”) is a software implementation of a computer that does not physically exist and is instead instantiated in an operating system of a physical computer (or host machine) to enable applications to execute within the VM's environment, i.e., a VM emulates a physical computer. A VM includes an operating system and associated virtual resources, such as computer memory and processor(s). A hypervisor operates between the VM and the hardware of the physical host machine and is generally responsible for creating and running the VMs. Hypervisors are also known in the art as virtual machine monitors or a virtual machine managers or “VMMs”, and may be implemented in software, firmware, and/or specialized hardware installed on the host machine. Examples of hypervisors include ESX Server, by VMware, Inc. of Palo Alto, Calif.; Microsoft Virtual Server and Microsoft Windows Server Hyper-V, both by Microsoft Corporation of Redmond, Wash.; Sun xVM by Oracle America Inc. of Santa Clara, Calif.; and Xen by Citrix Systems, Santa Clara, Calif. The hypervisor provides resources to each virtual operating system such as a virtual processor, virtual memory, a virtual network device, and a virtual disk. Each virtual machine has one or more associated virtual disks. The hypervisor typically stores the data of virtual disks in files on the file system of the physical host machine, called virtual machine disk files (“VMDK” in VMware lingo) or virtual hard disk image files (in Microsoft lingo). For example, VMware's ESX Server provides the Virtual Machine File System (VMFS) for the storage of virtual machine disk files. A virtual machine reads data from and writes data to its virtual disk much the way that a physical machine reads data from and writes data to a physical disk. Examples of techniques for implementing information management in a cloud computing environment are described in U.S. Pat. No. 8,285,681. Examples of techniques for implementing information management in a virtualized computing environment are described in U.S. Pat. No. 8,307,177.

Information management system 100 can also include electronic data storage devices, generally used for mass storage of data, including, e.g., primary storage devices 104 and secondary storage devices 108. Storage devices can generally be of any suitable type including, without limitation, disk drives, storage arrays (e.g., storage-area network (SAN) and/or network-attached storage (NAS) technology), semiconductor memory (e.g., solid state storage devices), network attached storage (NAS) devices, tape libraries, or other magnetic, non-tape storage devices, optical media storage devices, combinations of the same, etc. In some embodiments, storage devices form part of a distributed file system. In some cases, storage devices are provided in a cloud storage environment (e.g., a private cloud or one operated by a third-party vendor), whether for primary data or secondary copies or both.

Depending on context, the term “information management system” can refer to generally all of the illustrated hardware and software components in FIG. 1C, or the term may refer to only a subset of the illustrated components. For instance, in some cases, system 100 generally refers to a combination of specialized components used to protect, move, manage, manipulate, analyze, and/or process data and metadata generated by client computing devices 102. However, system 100 in some cases does not include the underlying components that generate and/or store primary data 112, such as the client computing devices 102 themselves, and the primary storage devices 104. Likewise secondary storage devices 108 (e.g., a third-party provided cloud storage environment) may not be part of system 100. As an example, “information management system” or “storage management system” may sometimes refer to one or more of the following components, which will be described in further detail below: storage manager, data agent, and media agent.

One or more client computing devices 102 may be part of system 100, each client computing device 102 having an operating system and at least one application 110 and one or more accompanying data agents executing thereon; and associated with one or more primary storage devices 104 storing primary data 112. Client computing device(s) 102 and primary storage devices 104 may generally be referred to in some cases as primary storage subsystem 117.

Client Computing Devices, Clients, and Subclients

Typically, a variety of sources in an organization produce data to be protected and managed. As just one illustrative example, in a corporate environment such data sources can be employee workstations and company servers such as a mail server, a web server, a database server, a transaction server, or the like. In system 100, data generation sources include one or more client computing devices 102. A computing device that has a data agent 142 installed and operating on it is generally referred to as a “client computing device” 102, and may include any type of computing device, without limitation. A client computing device 102 may be associated with one or more users and/or user accounts.

A “client” is a logical component of information management system 100, which may represent a logical grouping of one or more data agents installed on a client computing device 102. Storage manager 140 recognizes a client as a component of system 100, and in some embodiments, may automatically create a client component the first time a data agent 142 is installed on a client computing device 102. Because data generated by executable component(s) 110 is tracked by the associated data agent 142 so that it may be properly protected in system 100, a client may be said to generate data and to store the generated data to primary storage, such as primary storage device 104. However, the terms “client” and “client computing device” as used herein do not imply that a client computing device 102 is necessarily configured in the client/server sense relative to another computing device such as a mail server, or that a client computing device 102 cannot be a server in its own right. As just a few examples, a client computing device 102 can be and/or include mail servers, file servers, database servers, virtual machine servers, and/or web servers.

Each client computing device 102 may have application(s) 110 executing thereon which generate and manipulate the data that is to be protected from loss and managed in system 100. Applications 110 generally facilitate the operations of an organization, and can include, without limitation, mail server applications (e.g., Microsoft Exchange Server), file system applications, mail client applications (e.g., Microsoft Exchange Client), database applications or database management systems (e.g., SQL, Oracle, SAP, Lotus Notes Database), word processing applications (e.g., Microsoft Word), spreadsheet applications, financial applications, presentation applications, graphics and/or video applications, browser applications, mobile applications, entertainment applications, and so on. Each application 110 may be accompanied by an application-specific data agent 142, though not all data agents 142 are application-specific or associated with only application. A file manager application, e.g., Microsoft Windows Explorer, may be considered an application 110 and may be accompanied by its own data agent 142. Client computing devices 102 can have at least one operating system (e.g., Microsoft Windows, Mac OS X, iOS, IBM z/OS, Linux, other Unix-based operating systems, etc.) installed thereon, which may support or host one or more file systems and other applications 110. In some embodiments, a virtual machine that executes on a host client computing device 102 may be considered an application 110 and may be accompanied by a specific data agent 142 (e.g., virtual server data agent).

Client computing devices 102 and other components in system 100 can be connected to one another via one or more electronic communication pathways 114. For example, a first communication pathway 114 may communicatively couple client computing device 102 and secondary storage computing device 106; a second communication pathway 114 may communicatively couple storage manager 140 and client computing device 102; and a third communication pathway 114 may communicatively couple storage manager 140 and secondary storage computing device 106, etc. (see, e.g., FIG. 1A and FIG. 1C). A communication pathway 114 can include one or more networks or other connection types including one or more of the following, without limitation: the Internet, a wide area network (WAN), a local area network (LAN), a Storage Area Network (SAN), a Fibre Channel (FC) connection, a Small Computer System Interface (SCSI) connection, a virtual private network (VPN), a token ring or TCP/IP based network, an intranet network, a point-to-point link, a cellular network, a wireless data transmission system, a two-way cable system, an interactive kiosk network, a satellite network, a broadband network, a baseband network, a neural network, a mesh network, an ad hoc network, other appropriate computer or telecommunications networks, combinations of the same or the like. Communication pathways 114 in some cases may also include application programming interfaces (APIs) including, e.g., cloud service provider APIs, virtual machine management APIs, and hosted service provider APIs. The underlying infrastructure of communication pathways 114 may be wired and/or wireless, analog and/or digital, or any combination thereof; and the facilities used may be private, public, third-party provided, or any combination thereof, without limitation.

A “subclient” is a logical grouping of all or part of a client's primary data 112. In general, a subclient may be defined according to how the subclient data is to be protected as a unit in system 100. For example, a subclient may be associated with a certain storage policy. A given client may thus comprise several subclients, each subclient associated with a different storage policy. For example, some files may form a first subclient that requires compression and deduplication and is associated with a first storage policy. Other files of the client may form a second subclient that requires a different retention schedule as well as encryption, and may be associated with a different, second storage policy. As a result, though the primary data may be generated by the same application 110 and may belong to one given client, portions of the data may be assigned to different subclients for distinct treatment by system 100. More detail on subclients is given in regard to storage policies below.

Primary Data and Exemplary Primary Storage Devices

Primary data 112 is generally production data or “live” data generated by the operating system and/or applications 110 executing on client computing device 102. Primary data 112 is generally stored on primary storage device(s) 104 and is organized via a file system operating on the client computing device 102. Thus, client computing device(s) 102 and corresponding applications 110 may create, access, modify, write, delete, and otherwise use primary data 112. Primary data 112 is generally in the native format of the source application 110. Primary data 112 is an initial or first stored body of data generated by the source application 110. Primary data 112 in some cases is created substantially directly from data generated by the corresponding source application 110. It can be useful in performing certain tasks to organize primary data 112 into units of different granularities. In general, primary data 112 can include files, directories, file system volumes, data blocks, extents, or any other hierarchies or organizations of data objects. As used herein, a “data object” can refer to (i) any file that is currently addressable by a file system or that was previously addressable by the file system (e.g., an archive file), and/or to (ii) a subset of such a file (e.g., a data block, an extent, etc.). Primary data 112 may include structured data (e.g., database files), unstructured data (e.g., documents), and/or semi-structured data. See, e.g., FIG. 1B.

It can also be useful in performing certain functions of system 100 to access and modify metadata within primary data 112. Metadata generally includes information about data objects and/or characteristics associated with the data objects. For simplicity herein, it is to be understood that, unless expressly stated otherwise, any reference to primary data 112 generally also includes its associated metadata, but references to metadata generally do not include the primary data. Metadata can include, without limitation, one or more of the following: the data owner (e.g., the client or user that generates the data), the last modified time (e.g., the time of the most recent modification of the data object), a data object name (e.g., a file name), a data object size (e.g., a number of bytes of data), information about the content (e.g., an indication as to the existence of a particular search term), user-supplied tags, to/from information for email (e.g., an email sender, recipient, etc.), creation date, file type (e.g., format or application type), last accessed time, application type (e.g., type of application that generated the data object), location/network (e.g., a current, past or future location of the data object and network pathways to/from the data object), geographic location (e.g., GPS coordinates), frequency of change (e.g., a period in which the data object is modified), business unit (e.g., a group or department that generates, manages or is otherwise associated with the data object), aging information (e.g., a schedule, such as a time period, in which the data object is migrated to secondary or long term storage), boot sectors, partition layouts, file location within a file folder directory structure, user permissions, owners, groups, access control lists (ACLs), system metadata (e.g., registry information), combinations of the same or other similar information related to the data object. In addition to metadata generated by or related to file systems and operating systems, some applications 110 and/or other components of system 100 maintain indices of metadata for data objects, e.g., metadata associated with individual email messages. The use of metadata to perform classification and other functions is described in greater detail below.

Primary storage devices 104 storing primary data 112 may be relatively fast and/or expensive technology (e.g., flash storage, a disk drive, a hard-disk storage array, solid state memory, etc.), typically to support high-performance live production environments. Primary data 112 may be highly changeable and/or may be intended for relatively short term retention (e.g., hours, days, or weeks). According to some embodiments, client computing device 102 can access primary data 112 stored in primary storage device 104 by making conventional file system calls via the operating system. Each client computing device 102 is generally associated with and/or in communication with one or more primary storage devices 104 storing corresponding primary data 112. A client computing device 102 is said to be associated with or in communication with a particular primary storage device 104 if it is capable of one or more of: routing and/or storing data (e.g., primary data 112) to the primary storage device 104, coordinating the routing and/or storing of data to the primary storage device 104, retrieving data from the primary storage device 104, coordinating the retrieval of data from the primary storage device 104, and modifying and/or deleting data in the primary storage device 104. Thus, a client computing device 102 may be said to access data stored in an associated storage device 104.

Primary storage device 104 may be dedicated or shared. In some cases, each primary storage device 104 is dedicated to an associated client computing device 102, e.g., a local disk drive. In other cases, one or more primary storage devices 104 can be shared by multiple client computing devices 102, e.g., via a local network, in a cloud storage implementation, etc. As one example, primary storage device 104 can be a storage array shared by a group of client computing devices 102, such as EMC Clariion, EMC Symmetrix, EMC Celerra, Dell EqualLogic, IBM XIV, NetApp FAS, HP EVA, and HP 3PAR.

System 100 may also include hosted services (not shown), which may be hosted in some cases by an entity other than the organization that employs the other components of system 100. For instance, the hosted services may be provided by online service providers. Such service providers can provide social networking services, hosted email services, or hosted productivity applications or other hosted applications such as software-as-a-service (SaaS), platform-as-a-service (PaaS), application service providers (ASPs), cloud services, or other mechanisms for delivering functionality via a network. As it services users, each hosted service may generate additional data and metadata, which may be managed by system 100, e.g., as primary data 112. In some cases, the hosted services may be accessed using one of the applications 110. As an example, a hosted mail service may be accessed via browser running on a client computing device 102.

Secondary Copies and Exemplary Secondary Storage Devices

Primary data 112 stored on primary storage devices 104 may be compromised in some cases, such as when an employee deliberately or accidentally deletes or overwrites primary data 112. Or primary storage devices 104 can be damaged, lost, or otherwise corrupted. For recovery and/or regulatory compliance purposes, it is therefore useful to generate and maintain copies of primary data 112. Accordingly, system 100 includes one or more secondary storage computing devices 106 and one or more secondary storage devices 108 configured to create and store one or more secondary copies 116 of primary data 112 including its associated metadata. The secondary storage computing devices 106 and the secondary storage devices 108 may be referred to as secondary storage subsystem 118.

Secondary copies 116 can help in search and analysis efforts and meet other information management goals as well, such as: restoring data and/or metadata if an original version is lost (e.g., by deletion, corruption, or disaster); allowing point-in-time recovery; complying with regulatory data retention and electronic discovery (e-discovery) requirements; reducing utilized storage capacity in the production system and/or in secondary storage; facilitating organization and search of data; improving user access to data files across multiple computing devices and/or hosted services; and implementing data retention and pruning policies.

A secondary copy 116 can comprise a separate stored copy of data that is derived from one or more earlier-created stored copies (e.g., derived from primary data 112 or from another secondary copy 116). Secondary copies 116 can include point-in-time data, and may be intended for relatively long-term retention before some or all of the data is moved to other storage or discarded. In some cases, a secondary copy 116 may be in a different storage device than other previously stored copies; and/or may be remote from other previously stored copies. Secondary copies 116 can be stored in the same storage device as primary data 112. For example, a disk array capable of performing hardware snapshots stores primary data 112 and creates and stores hardware snapshots of the primary data 112 as secondary copies 116. Secondary copies 116 may be stored in relatively slow and/or lower cost storage (e.g., magnetic tape). A secondary copy 116 may be stored in a backup or archive format, or in some other format different from the native source application format or other format of primary data 112.

Secondary storage computing devices 106 may index secondary copies 116 (e.g., using a media agent 144), enabling users to browse and restore at a later time and further enabling the lifecycle management of the indexed data. After creation of a secondary copy 116 that represents certain primary data 112, a pointer or other location indicia (e.g., a stub) may be placed in primary data 112, or be otherwise associated with primary data 112, to indicate the current location of a particular secondary copy 116. Since an instance of a data object or metadata in primary data 112 may change over time as it is modified by application 110 (or hosted service or the operating system), system 100 may create and manage multiple secondary copies 116 of a particular data object or metadata, each copy representing the state of the data object in primary data 112 at a particular point in time. Moreover, since an instance of a data object in primary data 112 may eventually be deleted from primary storage device 104 and the file system, system 100 may continue to manage point-in-time representations of that data object, even though the instance in primary data 112 no longer exists. For virtual machines, the operating system and other applications 110 of client computing device(s) 102 may execute within or under the management of virtualization software (e.g., a VMM), and the primary storage device(s) 104 may comprise a virtual disk created on a physical storage device. System 100 may create secondary copies 116 of the files or other data objects in a virtual disk file and/or secondary copies 116 of the entire virtual disk file itself (e.g., of an entire .vmdk file).

Secondary copies 116 are distinguishable from corresponding primary data 112. First, secondary copies 116 can be stored in a different format from primary data 112 (e.g., backup, archive, or other non-native format). For this or other reasons, secondary copies 116 may not be directly usable by applications 110 or client computing device 102 (e.g., via standard system calls or otherwise) without modification, processing, or other intervention by system 100 which may be referred to as “restore” operations. Secondary copies 116 may have been processed by data agent 142 and/or media agent 144 in the course of being created (e.g., compression, deduplication, encryption, integrity markers, indexing, formatting, application-aware metadata, etc.), and thus secondary copy 116 may represent source primary data 112 without necessarily being exactly identical to the source.

Second, secondary copies 116 may be stored on a secondary storage device 108 that is inaccessible to application 110 running on client computing device 102 and/or hosted service. Some secondary copies 116 may be “offline copies,” in that they are not readily available (e.g., not mounted to tape or disk). Offline copies can include copies of data that system 100 can access without human intervention (e.g., tapes within an automated tape library, but not yet mounted in a drive), and copies that the system 100 can access only with some human intervention (e.g., tapes located at an offsite storage site).

Using Intermediate Devices for Creating Secondary Copies—Secondary Storage Computing Devices

Creating secondary copies can be challenging when hundreds or thousands of client computing devices 102 continually generate large volumes of primary data 112 to be protected. Also, there can be significant overhead involved in the creation of secondary copies 116. Moreover, specialized programmed intelligence and/or hardware capability is generally needed for accessing and interacting with secondary storage devices 108. Client computing devices 102 may interact directly with a secondary storage device 108 to create secondary copies 116, but in view of the factors described above, this approach can negatively impact the ability of client computing device 102 to serve/service application 110 and produce primary data 112. Further, any given client computing device 102 may not be optimized for interaction with certain secondary storage devices 108.

Thus, system 100 may include one or more software and/or hardware components which generally act as intermediaries between client computing devices 102 (that generate primary data 112) and secondary storage devices 108 (that store secondary copies 116). In addition to off-loading certain responsibilities from client computing devices 102, these intermediate components provide other benefits. For instance, as discussed further below with respect to FIG. 1D, distributing some of the work involved in creating secondary copies 116 can enhance scalability and improve system performance. For instance, using specialized secondary storage computing devices 106 and media agents 144 for interfacing with secondary storage devices 108 and/or for performing certain data processing operations can greatly improve the speed with which system 100 performs information management operations and can also improve the capacity of the system to handle large numbers of such operations, while reducing the computational load on the production environment of client computing devices 102. The intermediate components can include one or more secondary storage computing devices 106 as shown in FIG. 1A and/or one or more media agents 144. Media agents are discussed further below (e.g., with respect to FIGS. 1C-1E). These special-purpose components of system 100 comprise specialized programmed intelligence and/or hardware capability for writing to, reading from, instructing, communicating with, or otherwise interacting with secondary storage devices 108.

Secondary storage computing device(s) 106 can comprise any of the computing devices described above, without limitation. In some cases, secondary storage computing device(s) 106 also include specialized hardware componentry and/or software intelligence (e.g., specialized interfaces) for interacting with certain secondary storage device(s) 108 with which they may be specially associated.

To create a secondary copy 116 involving the copying of data from primary storage subsystem 117 to secondary storage subsystem 118, client computing device 102 may communicate the primary data 112 to be copied (or a processed version thereof generated by a data agent 142) to the designated secondary storage computing device 106, via a communication pathway 114. Secondary storage computing device 106 in turn may further process and convey the data or a processed version thereof to secondary storage device 108. One or more secondary copies 116 may be created from existing secondary copies 116, such as in the case of an auxiliary copy operation, described further below.

Exemplary Primary Data and an Exemplary Secondary Copy

FIG. 16 is a detailed view of some specific examples of primary data stored on primary storage device(s) 104 and secondary copy data stored on secondary storage device(s) 108, with other components of the system removed for the purposes of illustration. Stored on primary storage device(s) 104 are primary data 112 objects including word processing documents 119A-B, spreadsheets 120, presentation documents 122, video files 124, image files 126, email mailboxes 128 (and corresponding email messages 129A-C), HTML/XML or other types of markup language files 130, databases 132 and corresponding tables or other data structures 133A-133C. Some or all primary data 112 objects are associated with corresponding metadata (e.g., “Meta1-11”), which may include file system metadata and/or application-specific metadata. Stored on the secondary storage device(s) 108 are secondary copy 116 data objects 134A-C which may include copies of or may otherwise represent corresponding primary data 112.

Secondary copy data objects 134A-C can individually represent more than one primary data object. For example, secondary copy data object 134A represents three separate primary data objects 133C, 122, and 129C (represented as 133C′, 122′, and 129C′, respectively, and accompanied by corresponding metadata Metal1, Meta3, and Meta8, respectively). Moreover, as indicated by the prime mark (′), secondary storage computing devices 106 or other components in secondary storage subsystem 118 may process the data received from primary storage subsystem 117 and store a secondary copy including a transformed and/or supplemented representation of a primary data object and/or metadata that is different from the original format, e.g., in a compressed, encrypted, deduplicated, or other modified format. For instance, secondary storage computing devices 106 can generate new metadata or other information based on said processing, and store the newly generated information along with the secondary copies. Secondary copy data object 1346 represents primary data objects 120, 1336, and 119A as 120′, 1336′, and 119A′, respectively, accompanied by corresponding metadata Meta2, Meta10, and Meta1, respectively. Also, secondary copy data object 134C represents primary data objects 133A, 1196, and 129A as 133A′, 1196′, and 129A′, respectively, accompanied by corresponding metadata Meta9, Meta5, and Meta6, respectively.

Exemplary Information Management System Architecture

System 100 can incorporate a variety of different hardware and software components, which can in turn be organized with respect to one another in many different configurations, depending on the embodiment. There are critical design choices involved in specifying the functional responsibilities of the components and the role of each component in system 100. Such design choices can impact how system 100 performs and adapts to data growth and other changing circumstances. FIG. 1C shows a system 100 designed according to these considerations and includes: storage manager 140, one or more data agents 142 executing on client computing device(s) 102 and configured to process primary data 112, and one or more media agents 144 executing on one or more secondary storage computing devices 106 for performing tasks involving secondary storage devices 108.

Storage Manager

Storage manager 140 is a centralized storage and/or information manager that is configured to perform certain control functions and also to store certain critical information about system 100—hence storage manager 140 is said to manage system 100. As noted, the number of components in system 100 and the amount of data under management can be large. Managing the components and data is therefore a significant task, which can grow unpredictably as the number of components and data scale to meet the needs of the organization. For these and other reasons, according to certain embodiments, responsibility for controlling system 100, or at least a significant portion of that responsibility, is allocated to storage manager 140. Storage manager 140 can be adapted independently according to changing circumstances, without having to replace or re-design the remainder of the system. Moreover, a computing device for hosting and/or operating as storage manager 140 can be selected to best suit the functions and networking needs of storage manager 140. These and other advantages are described in further detail below and with respect to FIG. 1D.

Storage manager 140 may be a software module or other application hosted by a suitable computing device. In some embodiments, storage manager 140 is itself a computing device that performs the functions described herein. Storage manager 140 comprises or operates in conjunction with one or more associated data structures such as a dedicated database (e.g., management database 146), depending on the configuration. The storage manager 140 generally initiates, performs, coordinates, and/or controls storage and other information management operations performed by system 100, e.g., to protect and control primary data 112 and secondary copies 116. In general, storage manager 140 is said to manage system 100, which includes communicating with, instructing, and controlling in some circumstances components such as data agents 142 and media agents 144, etc.

As shown by the dashed arrowed lines 114 in FIG. 1C, storage manager 140 may communicate with, instruct, and/or control some or all elements of system 100, such as data agents 142 and media agents 144. In this manner, storage manager 140 manages the operation of various hardware and software components in system 100. In certain embodiments, control information originates from storage manager 140 and status as well as index reporting is transmitted to storage manager 140 by the managed components, whereas payload data and metadata are generally communicated between data agents 142 and media agents 144 (or otherwise between client computing device(s) 102 and secondary storage computing device(s) 106), e.g., at the direction of and under the management of storage manager 140. Control information can generally include parameters and instructions for carrying out information management operations, such as, without limitation, instructions to perform a task associated with an operation, timing information specifying when to initiate a task, data path information specifying what components to communicate with or access in carrying out an operation, and the like. In other embodiments, some information management operations are controlled or initiated by other components of system 100 (e.g., by media agents 144 or data agents 142), instead of or in combination with storage manager 140.

According to certain embodiments, storage manager 140 provides one or more of the following functions:

communicating with data agents 142 and media agents 144, including transmitting instructions, messages, and/or queries, as well as receiving status reports, index information, messages, and/or queries, and responding to same;

-   -   initiating execution of information management operations;     -   initiating restore and recovery operations;     -   managing secondary storage devices 108 and inventory/capacity of         the same;     -   allocating secondary storage devices 108 for secondary copy         operations;     -   reporting, searching, and/or classification of data in system         100;     -   monitoring completion of and status reporting related to         information management operations and jobs;     -   tracking movement of data within system 100;     -   tracking age information relating to secondary copies 116,         secondary storage devices 108, comparing the age information         against retention guidelines, and initiating data pruning when         appropriate;     -   tracking logical associations between components in system 100;     -   protecting metadata associated with system 100, e.g., in         management database 146;     -   implementing job management, schedule management, event         management, alert management, reporting, job history         maintenance, user security management, disaster recovery         management, and/or user interfacing for system administrators         and/or end users of system 100;     -   sending, searching, and/or viewing of log files; and     -   implementing operations management functionality.

Storage manager 140 may maintain an associated database 146 (or “storage manager database 146” or “management database 146”) of management-related data and information management policies 148. Database 146 is stored in computer memory accessible by storage manager 140. Database 146 may include a management index 150 (or “index 150”) or other data structure(s) that may store: logical associations between components of the system; user preferences and/or profiles (e.g., preferences regarding encryption, compression, or deduplication of primary data or secondary copies; preferences regarding the scheduling, type, or other aspects of secondary copy or other operations; mappings of particular information management users or user accounts to certain computing devices or other components, etc.; management tasks; media containerization; other useful data; and/or any combination thereof. For example, storage manager 140 may use index 150 to track logical associations between media agents 144 and secondary storage devices 108 and/or movement of data to/from secondary storage devices 108. For instance, index 150 may store data associating a client computing device 102 with a particular media agent 144 and/or secondary storage device 108, as specified in an information management policy 148.

Administrators and others may configure and initiate certain information management operations on an individual basis. But while this may be acceptable for some recovery operations or other infrequent tasks, it is often not workable for implementing on-going organization-wide data protection and management. Thus, system 100 may utilize information management policies 148 for specifying and executing information management operations on an automated basis. Generally, an information management policy 148 can include a stored data structure or other information source that specifies parameters (e.g., criteria and rules) associated with storage management or other information management operations. Storage manager 140 can process an information management policy 148 and/or index 150 and, based on the results, identify an information management operation to perform, identify the appropriate components in system 100 to be involved in the operation (e.g., client computing devices 102 and corresponding data agents 142, secondary storage computing devices 106 and corresponding media agents 144, etc.), establish connections to those components and/or between those components, and/or instruct and control those components to carry out the operation. In this manner, system 100 can translate stored information into coordinated activity among the various computing devices in system 100.

Management database 146 may maintain information management policies 148 and associated data, although information management policies 148 can be stored in computer memory at any appropriate location outside management database 146. For instance, an information management policy 148 such as a storage policy may be stored as metadata in a media agent database 152 or in a secondary storage device 108 (e.g., as an archive copy) for use in restore or other information management operations, depending on the embodiment. Information management policies 148 are described further below. According to certain embodiments, management database 146 comprises a relational database (e.g., an SQL database) for tracking metadata, such as metadata associated with secondary copy operations (e.g., what client computing devices 102 and corresponding subclient data were protected and where the secondary copies are stored and which media agent 144 performed the storage operation(s)). This and other metadata may additionally be stored in other locations, such as at secondary storage computing device 106 or on the secondary storage device 108, allowing data recovery without the use of storage manager 140 in some cases. Thus, management database 146 may comprise data needed to kick off secondary copy operations (e.g., storage policies, schedule policies, etc.), status and reporting information about completed jobs (e.g., status and error reports on yesterday's backup jobs), and additional information sufficient to enable restore and disaster recovery operations (e.g., media agent associations, location indexing, content indexing, etc.).

Storage manager 140 may include a jobs agent 156, a user interface 158, and a management agent 154, all of which may be implemented as interconnected software modules or application programs. These are described further below.

Jobs agent 156 in some embodiments initiates, controls, and/or monitors the status of some or all information management operations previously performed, currently being performed, or scheduled to be performed by system 100. A job is a logical grouping of information management operations such as daily storage operations scheduled for a certain set of subclients (e.g., generating incremental block-level backup copies 116 at a certain time every day for database files in a certain geographical location). Thus, jobs agent 156 may access information management policies 148 (e.g., in management database 146) to determine when, where, and how to initiate/control jobs in system 100.

Storage Manager User Interfaces

User interface 158 may include information processing and display software, such as a graphical user interface (GUI), an application program interface (API), and/or other interactive interface(s) through which users and system processes can retrieve information about the status of information management operations or issue instructions to storage manager 140 and other components. Via user interface 158, users may issue instructions to the components in system 100 regarding performance of secondary copy and recovery operations. For example, a user may modify a schedule concerning the number of pending secondary copy operations. As another example, a user may employ the GUI to view the status of pending secondary copy jobs or to monitor the status of certain components in system 100 (e.g., the amount of capacity left in a storage device). Storage manager 140 may track information that permits it to select, designate, or otherwise identify content indices, deduplication databases, or similar databases or resources or data sets within its information management cell (or another cell) to be searched in response to certain queries. Such queries may be entered by the user by interacting with user interface 158.

Various embodiments of information management system 100 may be configured and/or designed to generate user interface data usable for rendering the various interactive user interfaces described. The user interface data may be used by system 100 and/or by another system, device, and/or software program (for example, a browser program), to render the interactive user interfaces. The interactive user interfaces may be displayed on, for example, electronic displays (including, for example, touch-enabled displays), consoles, etc., whether direct-connected to storage manager 140 or communicatively coupled remotely, e.g., via an internet connection. The present disclosure describes various embodiments of interactive and dynamic user interfaces, some of which may be generated by user interface agent 158, and which are the result of significant technological development. The user interfaces described herein may provide improved human-computer interactions, allowing for significant cognitive and ergonomic efficiencies and advantages over previous systems, including reduced mental workloads, improved decision-making, and the like. User interface 158 may operate in a single integrated view or console (not shown). The console may support a reporting capability for generating a variety of reports, which may be tailored to a particular aspect of information management.

User interfaces are not exclusive to storage manager 140 and in some embodiments a user may access information locally from a computing device component of system 100. For example, some information pertaining to installed data agents 142 and associated data streams may be available from client computing device 102. Likewise, some information pertaining to media agents 144 and associated data streams may be available from secondary storage computing device 106.

Storage Manager Management Agent

Management agent 154 can provide storage manager 140 with the ability to communicate with other components within system 100 and/or with other information management cells via network protocols and application programming interfaces (APIs) including, e.g., HTTP, HTTPS, FTP, REST, virtualization software APIs, cloud service provider APIs, and hosted service provider APIs, without limitation. Management agent 154 also allows multiple information management cells to communicate with one another. For example, system 100 in some cases may be one information management cell in a network of multiple cells adjacent to one another or otherwise logically related, e.g., in a WAN or LAN. With this arrangement, the cells may communicate with one another through respective management agents 154. Inter-cell communications and hierarchy is described in greater detail in e.g., U.S. Pat. No. 7,343,453.

Information Management Cell

An “information management cell” (or “storage operation cell” or “cell”) may generally include a logical and/or physical grouping of a combination of hardware and software components associated with performing information management operations on electronic data, typically one storage manager 140 and at least one data agent 142 (executing on a client computing device 102) and at least one media agent 144 (executing on a secondary storage computing device 106). For instance, the components shown in FIG. 1C may together form an information management cell. Thus, in some configurations, a system 100 may be referred to as an information management cell or a storage operation cell. A given cell may be identified by the identity of its storage manager 140, which is generally responsible for managing the cell.

Multiple cells may be organized hierarchically, so that cells may inherit properties from hierarchically superior cells or be controlled by other cells in the hierarchy (automatically or otherwise). Alternatively, in some embodiments, cells may inherit or otherwise be associated with information management policies, preferences, information management operational parameters, or other properties or characteristics according to their relative position in a hierarchy of cells. Cells may also be organized hierarchically according to function, geography, architectural considerations, or other factors useful or desirable in performing information management operations. For example, a first cell may represent a geographic segment of an enterprise, such as a Chicago office, and a second cell may represent a different geographic segment, such as a New York City office. Other cells may represent departments within a particular office, e.g., human resources, finance, engineering, etc. Where delineated by function, a first cell may perform one or more first types of information management operations (e.g., one or more first types of secondary copies at a certain frequency), and a second cell may perform one or more second types of information management operations (e.g., one or more second types of secondary copies at a different frequency and under different retention rules). In general, the hierarchical information is maintained by one or more storage managers 140 that manage the respective cells (e.g., in corresponding management database(s) 146).

Data Agents

A variety of different applications 110 can operate on a given client computing device 102, including operating systems, file systems, database applications, e-mail applications, and virtual machines, just to name a few. And, as part of the process of creating and restoring secondary copies 116, the client computing device 102 may be tasked with processing and preparing the primary data 112 generated by these various applications 110. Moreover, the nature of the processing/preparation can differ across application types, e.g., due to inherent structural, state, and formatting differences among applications 110 and/or the operating system of client computing device 102. Each data agent 142 is therefore advantageously configured in some embodiments to assist in the performance of information management operations based on the type of data that is being protected at a client-specific and/or application-specific level.

Data agent 142 is a component of information system 100 and is generally directed by storage manager 140 to participate in creating or restoring secondary copies 116. Data agent 142 may be a software program (e.g., in the form of a set of executable binary files) that executes on the same client computing device 102 as the associated application 110 that data agent 142 is configured to protect. Data agent 142 is generally responsible for managing, initiating, or otherwise assisting in the performance of information management operations in reference to its associated application(s) 110 and corresponding primary data 112 which is generated/accessed by the particular application(s) 110. For instance, data agent 142 may take part in copying, archiving, migrating, and/or replicating of certain primary data 112 stored in the primary storage device(s) 104. Data agent 142 may receive control information from storage manager 140, such as commands to transfer copies of data objects and/or metadata to one or more media agents 144. Data agent 142 also may compress, deduplicate, and encrypt certain primary data 112, as well as capture application-related metadata before transmitting the processed data to media agent 144. Data agent 142 also may receive instructions from storage manager 140 to restore (or assist in restoring) a secondary copy 116 from secondary storage device 108 to primary storage 104, such that the restored data may be properly accessed by application 110 in a suitable format as though it were primary data 112.

Each data agent 142 may be specialized for a particular application 110. For instance, different individual data agents 142 may be designed to handle Microsoft Exchange data, Lotus Notes data, Microsoft Windows file system data, Microsoft Active Directory Objects data, SQL Server data, Share Point data, Oracle database data, SAP database data, virtual machines and/or associated data, and other types of data. A file system data agent, for example, may handle data files and/or other file system information. If a client computing device 102 has two or more types of data 112, a specialized data agent 142 may be used for each data type. For example, to backup, migrate, and/or restore all of the data on a Microsoft Exchange server, the client computing device 102 may use: (1) a Microsoft Exchange Mailbox data agent 142 to back up the Exchange mailboxes; (2) a Microsoft Exchange Database data agent 142 to back up the Exchange databases; (3) a Microsoft Exchange Public Folder data agent 142 to back up the Exchange Public Folders; and (4) a Microsoft Windows File System data agent 142 to back up the file system of client computing device 102. In this example, these specialized data agents 142 are treated as four separate data agents 142 even though they operate on the same client computing device 102. Other examples may include archive management data agents such as a migration archiver or a compliance archiver, Quick Recovery® agents, and continuous data replication agents. Application-specific data agents 142 can provide improved performance as compared to generic agents. For instance, because application-specific data agents 142 may only handle data for a single software application, the design, operation, and performance of the data agent 142 can be streamlined. The data agent 142 may therefore execute faster and consume less persistent storage and/or operating memory than data agents designed to generically accommodate multiple different software applications 110.

Each data agent 142 may be configured to access data and/or metadata stored in the primary storage device(s) 104 associated with data agent 142 and its host client computing device 102, and process the data appropriately. For example, during a secondary copy operation, data agent 142 may arrange or assemble the data and metadata into one or more files having a certain format (e.g., a particular backup or archive format) before transferring the file(s) to a media agent 144 or other component. The file(s) may include a list of files or other metadata. In some embodiments, a data agent 142 may be distributed between client computing device 102 and storage manager 140 (and any other intermediate components) or may be deployed from a remote location or its functions approximated by a remote process that performs some or all of the functions of data agent 142. In addition, a data agent 142 may perform some functions provided by media agent 144. Other embodiments may employ one or more generic data agents 142 that can handle and process data from two or more different applications 110, or that can handle and process multiple data types, instead of or in addition to using specialized data agents 142. For example, one generic data agent 142 may be used to back up, migrate and restore Microsoft Exchange Mailbox data and Microsoft Exchange Database data, while another generic data agent may handle Microsoft Exchange Public Folder data and Microsoft Windows File System data.

Media Agents

As noted, off-loading certain responsibilities from client computing devices 102 to intermediate components such as secondary storage computing device(s) 106 and corresponding media agent(s) 144 can provide a number of benefits including improved performance of client computing device 102, faster and more reliable information management operations, and enhanced scalability. In one example which will be discussed further below, media agent 144 can act as a local cache of recently-copied data and/or metadata stored to secondary storage device(s) 108, thus improving restore capabilities and performance for the cached data.

Media agent 144 is a component of system 100 and is generally directed by storage manager 140 in creating and restoring secondary copies 116. Whereas storage manager 140 generally manages system 100 as a whole, media agent 144 provides a portal to certain secondary storage devices 108, such as by having specialized features for communicating with and accessing certain associated secondary storage device 108. Media agent 144 may be a software program (e.g., in the form of a set of executable binary files) that executes on a secondary storage computing device 106. Media agent 144 generally manages, coordinates, and facilitates the transmission of data between a data agent 142 (executing on client computing device 102) and secondary storage device(s) 108 associated with media agent 144. For instance, other components in the system may interact with media agent 144 to gain access to data stored on associated secondary storage device(s) 108, (e.g., to browse, read, write, modify, delete, or restore data). Moreover, media agents 144 can generate and store information relating to characteristics of the stored data and/or metadata, or can generate and store other types of information that generally provides insight into the contents of the secondary storage devices 108—generally referred to as indexing of the stored secondary copies 116. Each media agent 144 may operate on a dedicated secondary storage computing device 106, while in other embodiments a plurality of media agents 144 may operate on the same secondary storage computing device 106.

A media agent 144 may be associated with a particular secondary storage device 108 if that media agent 144 is capable of one or more of: routing and/or storing data to the particular secondary storage device 108; coordinating the routing and/or storing of data to the particular secondary storage device 108; retrieving data from the particular secondary storage device 108; coordinating the retrieval of data from the particular secondary storage device 108; and modifying and/or deleting data retrieved from the particular secondary storage device 108. Media agent 144 in certain embodiments is physically separate from the associated secondary storage device 108. For instance, a media agent 144 may operate on a secondary storage computing device 106 in a distinct housing, package, and/or location from the associated secondary storage device 108. In one example, a media agent 144 operates on a first server computer and is in communication with a secondary storage device(s) 108 operating in a separate rack-mounted RAID-based system.

A media agent 144 associated with a particular secondary storage device 108 may instruct secondary storage device 108 to perform an information management task. For instance, a media agent 144 may instruct a tape library to use a robotic arm or other retrieval means to load or eject a certain storage media, and to subsequently archive, migrate, or retrieve data to or from that media, e.g., for the purpose of restoring data to a client computing device 102. As another example, a secondary storage device 108 may include an array of hard disk drives or solid state drives organized in a RAID configuration, and media agent 144 may forward a logical unit number (LUN) and other appropriate information to the array, which uses the received information to execute the desired secondary copy operation. Media agent 144 may communicate with a secondary storage device 108 via a suitable communications link, such as a SCSI or Fibre Channel link.

Each media agent 144 may maintain an associated media agent database 152. Media agent database 152 may be stored to a disk or other storage device (not shown) that is local to the secondary storage computing device 106 on which media agent 144 executes. In other cases, media agent database 152 is stored separately from the host secondary storage computing device 106. Media agent database 152 can include, among other things, a media agent index 153 (see, e.g., FIG. 1C). In some cases, media agent index 153 does not form a part of and is instead separate from media agent database 152.

Media agent index 153 (or “index 153”) may be a data structure associated with the particular media agent 144 that includes information about the stored data associated with the particular media agent and which may be generated in the course of performing a secondary copy operation or a restore. Index 153 provides a fast and efficient mechanism for locating/browsing secondary copies 116 or other data stored in secondary storage devices 108 without having to access secondary storage device 108 to retrieve the information from there. For instance, for each secondary copy 116, index 153 may include metadata such as a list of the data objects (e.g., files/subdirectories, database objects, mailbox objects, etc.), a logical path to the secondary copy 116 on the corresponding secondary storage device 108, location information (e.g., offsets) indicating where the data objects are stored in the secondary storage device 108, when the data objects were created or modified, etc. Thus, index 153 includes metadata associated with the secondary copies 116 that is readily available for use from media agent 144. In some embodiments, some or all of the information in index 153 may instead or additionally be stored along with secondary copies 116 in secondary storage device 108. In some embodiments, a secondary storage device 108 can include sufficient information to enable a “bare metal restore,” where the operating system and/or software applications of a failed client computing device 102 or another target may be automatically restored without manually reinstalling individual software packages (including operating systems).

Because index 153 may operate as a cache, it can also be referred to as an “index cache.” In such cases, information stored in index cache 153 typically comprises data that reflects certain particulars about relatively recent secondary copy operations. After some triggering event, such as after some time elapses or index cache 153 reaches a particular size, certain portions of index cache 153 may be copied or migrated to secondary storage device 108, e.g., on a least-recently-used basis. This information may be retrieved and uploaded back into index cache 153 or otherwise restored to media agent 144 to facilitate retrieval of data from the secondary storage device(s) 108. In some embodiments, the cached information may include format or containerization information related to archives or other files stored on storage device(s) 108.

In some alternative embodiments media agent 144 generally acts as a coordinator or facilitator of secondary copy operations between client computing devices 102 and secondary storage devices 108, but does not actually write the data to secondary storage device 108. For instance, storage manager 140 (or media agent 144) may instruct a client computing device 102 and secondary storage device 108 to communicate with one another directly. In such a case, client computing device 102 transmits data directly or via one or more intermediary components to secondary storage device 108 according to the received instructions, and vice versa. Media agent 144 may still receive, process, and/or maintain metadata related to the secondary copy operations, i.e., may continue to build and maintain index 153. In these embodiments, payload data can flow through media agent 144 for the purposes of populating index 153, but not for writing to secondary storage device 108. Media agent 144 and/or other components such as storage manager 140 may in some cases incorporate additional functionality, such as data classification, content indexing, deduplication, encryption, compression, and the like. Further details regarding these and other functions are described below.

Distributed, Scalable Architecture

As described, certain functions of system 100 can be distributed amongst various physical and/or logical components. For instance, one or more of storage manager 140, data agents 142, and media agents 144 may operate on computing devices that are physically separate from one another. This architecture can provide a number of benefits. For instance, hardware and software design choices for each distributed component can be targeted to suit its particular function. The secondary computing devices 106 on which media agents 144 operate can be tailored for interaction with associated secondary storage devices 108 and provide fast index cache operation, among other specific tasks. Similarly, client computing device(s) 102 can be selected to effectively service applications 110 in order to efficiently produce and store primary data 112.

Moreover, in some cases, one or more of the individual components of information management system 100 can be distributed to multiple separate computing devices. As one example, for large file systems where the amount of data stored in management database 146 is relatively large, database 146 may be migrated to or may otherwise reside on a specialized database server (e.g., an SQL server) separate from a server that implements the other functions of storage manager 140. This distributed configuration can provide added protection because database 146 can be protected with standard database utilities (e.g., SQL log shipping or database replication) independent from other functions of storage manager 140. Database 146 can be efficiently replicated to a remote site for use in the event of a disaster or other data loss at the primary site. Or database 146 can be replicated to another computing device within the same site, such as to a higher performance machine in the event that a storage manager host computing device can no longer service the needs of a growing system 100.

The distributed architecture also provides scalability and efficient component utilization. FIG. 1D shows an embodiment of information management system 100 including a plurality of client computing devices 102 and associated data agents 142 as well as a plurality of secondary storage computing devices 106 and associated media agents 144. Additional components can be added or subtracted based on the evolving needs of system 100. For instance, depending on where bottlenecks are identified, administrators can add additional client computing devices 102, secondary storage computing devices 106, and/or secondary storage devices 108. Moreover, where multiple fungible components are available, load balancing can be implemented to dynamically address identified bottlenecks. As an example, storage manager 140 may dynamically select which media agents 144 and/or secondary storage devices 108 to use for storage operations based on a processing load analysis of media agents 144 and/or secondary storage devices 108, respectively.

Where system 100 includes multiple media agents 144 (see, e.g., FIG. 1D), a first media agent 144 may provide failover functionality for a second failed media agent 144. In addition, media agents 144 can be dynamically selected to provide load balancing. Each client computing device 102 can communicate with, among other components, any of the media agents 144, e.g., as directed by storage manager 140. And each media agent 144 may communicate with, among other components, any of secondary storage devices 108, e.g., as directed by storage manager 140. Thus, operations can be routed to secondary storage devices 108 in a dynamic and highly flexible manner, to provide load balancing, failover, etc. Further examples of scalable systems capable of dynamic storage operations, load balancing, and failover are provided in U.S. Pat. No. 7,246,207.

While distributing functionality amongst multiple computing devices can have certain advantages, in other contexts it can be beneficial to consolidate functionality on the same computing device. In alternative configurations, certain components may reside and execute on the same computing device. As such, in other embodiments, one or more of the components shown in FIG. 1C may be implemented on the same computing device. In one configuration, a storage manager 140, one or more data agents 142, and/or one or more media agents 144 are all implemented on the same computing device. In other embodiments, one or more data agents 142 and one or more media agents 144 are implemented on the same computing device, while storage manager 140 is implemented on a separate computing device, etc. without limitation.

Exemplary Types of Information Management Operations, Including Storage Operations

In order to protect and leverage stored data, system 100 can be configured to perform a variety of information management operations, which may also be referred to in some cases as storage management operations or storage operations. These operations can generally include (i) data movement operations, (ii) processing and data manipulation operations, and (iii) analysis, reporting, and management operations.

Data Movement Operations, Including Secondary Copy Operations

Data movement operations are generally storage operations that involve the copying or migration of data between different locations in system 100. For example, data movement operations can include operations in which stored data is copied, migrated, or otherwise transferred from one or more first storage devices to one or more second storage devices, such as from primary storage device(s) 104 to secondary storage device(s) 108, from secondary storage device(s) 108 to different secondary storage device(s) 108, from secondary storage devices 108 to primary storage devices 104, or from primary storage device(s) 104 to different primary storage device(s) 104, or in some cases within the same primary storage device 104 such as within a storage array.

Data movement operations can include by way of example, backup operations, archive operations, information lifecycle management operations such as hierarchical storage management operations, replication operations (e.g., continuous data replication), snapshot operations, deduplication or single-instancing operations, auxiliary copy operations, disaster-recovery copy operations, and the like. As will be discussed, some of these operations do not necessarily create distinct copies. Nonetheless, some or all of these operations are generally referred to as “secondary copy operations” for simplicity, because they involve secondary copies. Data movement also comprises restoring secondary copies.

Backup Operations

A backup operation creates a copy of a version of primary data 112 at a particular point in time (e.g., one or more files or other data units). Each subsequent backup copy 116 (which is a form of secondary copy 116) may be maintained independently of the first. A backup generally involves maintaining a version of the copied primary data 112 as well as backup copies 116. Further, a backup copy in some embodiments is generally stored in a form that is different from the native format, e.g., a backup format. This contrasts to the version in primary data 112 which may instead be stored in a format native to the source application(s) 110. In various cases, backup copies can be stored in a format in which the data is compressed, encrypted, deduplicated, and/or otherwise modified from the original native application format. For example, a backup copy may be stored in a compressed backup format that facilitates efficient long-term storage. Backup copies 116 can have relatively long retention periods as compared to primary data 112, which is generally highly changeable. Backup copies 116 may be stored on media with slower retrieval times than primary storage device 104. Some backup copies may have shorter retention periods than some other types of secondary copies 116, such as archive copies (described below). Backups may be stored at an offsite location.

Backup operations can include full backups, differential backups, incremental backups, “synthetic full” backups, and/or creating a “reference copy.” A full backup (or “standard full backup”) in some embodiments is generally a complete image of the data to be protected. However, because full backup copies can consume a relatively large amount of storage, it can be useful to use a full backup copy as a baseline and only store changes relative to the full backup copy afterwards.

A differential backup operation (or cumulative incremental backup operation) tracks and stores changes that occurred since the last full backup. Differential backups can grow quickly in size, but can restore relatively efficiently because a restore can be completed in some cases using only the full backup copy and the latest differential copy.

An incremental backup operation generally tracks and stores changes since the most recent backup copy of any type, which can greatly reduce storage utilization. In some cases, however, restoring can be lengthy compared to full or differential backups because completing a restore operation may involve accessing a full backup in addition to multiple incremental backups.

Synthetic full backups generally consolidate data without directly backing up data from the client computing device. A synthetic full backup is created from the most recent full backup (i.e., standard or synthetic) and subsequent incremental and/or differential backups. The resulting synthetic full backup is identical to what would have been created had the last backup for the subclient been a standard full backup. Unlike standard full, incremental, and differential backups, however, a synthetic full backup does not actually transfer data from primary storage to the backup media, because it operates as a backup consolidator. A synthetic full backup extracts the index data of each participating subclient. Using this index data and the previously backed up user data images, it builds new full backup images (e.g., bitmaps), one for each subclient. The new backup images consolidate the index and user data stored in the related incremental, differential, and previous full backups into a synthetic backup file that fully represents the subclient (e.g., via pointers) but does not comprise all its constituent data.

Any of the above types of backup operations can be at the volume level, file level, or block level. Volume level backup operations generally involve copying of a data volume (e.g., a logical disk or partition) as a whole. In a file-level backup, information management system 100 generally tracks changes to individual files and includes copies of files in the backup copy. For block-level backups, files are broken into constituent blocks, and changes are tracked at the block level. Upon restore, system 100 reassembles the blocks into files in a transparent fashion. Far less data may actually be transferred and copied to secondary storage devices 108 during a file-level copy than a volume-level copy. Likewise, a block-level copy may transfer less data than a file-level copy, resulting in faster execution. However, restoring a relatively higher-granularity copy can result in longer restore times. For instance, when restoring a block-level copy, the process of locating and retrieving constituent blocks can sometimes take longer than restoring file-level backups.

A reference copy may comprise copy(ies) of selected objects from backed up data, typically to help organize data by keeping contextual information from multiple sources together, and/or help retain specific data for a longer period of time, such as for legal hold needs. A reference copy generally maintains data integrity, and when the data is restored, it may be viewed in the same format as the source data. In some embodiments, a reference copy is based on a specialized client, individual subclient and associated information management policies (e.g., storage policy, retention policy, etc.) that are administered within system 100.

Archive Operations

Because backup operations generally involve maintaining a version of the copied primary data 112 and also maintaining backup copies in secondary storage device(s) 108, they can consume significant storage capacity. To reduce storage consumption, an archive operation according to certain embodiments creates an archive copy 116 by both copying and removing source data. Or, seen another way, archive operations can involve moving some or all of the source data to the archive destination. Thus, data satisfying criteria for removal (e.g., data of a threshold age or size) may be removed from source storage. The source data may be primary data 112 or a secondary copy 116, depending on the situation. As with backup copies, archive copies can be stored in a format in which the data is compressed, encrypted, deduplicated, and/or otherwise modified from the format of the original application or source copy. In addition, archive copies may be retained for relatively long periods of time (e.g., years) and, in some cases are never deleted. In certain embodiments, archive copies may be made and kept for extended periods in order to meet compliance regulations.

Archiving can also serve the purpose of freeing up space in primary storage device(s) 104 and easing the demand on computational resources on client computing device 102. Similarly, when a secondary copy 116 is archived, the archive copy can therefore serve the purpose of freeing up space in the source secondary storage device(s) 108. Examples of data archiving operations are provided in U.S. Pat. No. 7,107,298.

Snapshot Operations

Snapshot operations can provide a relatively lightweight, efficient mechanism for protecting data. From an end-user viewpoint, a snapshot may be thought of as an “instant” image of primary data 112 at a given point in time, and may include state and/or status information relative to an application 110 that creates/manages primary data 112. In one embodiment, a snapshot may generally capture the directory structure of an object in primary data 112 such as a file or volume or other data set at a particular moment in time and may also preserve file attributes and contents. A snapshot in some cases is created relatively quickly, e.g., substantially instantly, using a minimum amount of file space, but may still function as a conventional file system backup.

A “hardware snapshot” (or “hardware-based snapshot”) operation occurs where a target storage device (e.g., a primary storage device 104 or a secondary storage device 108) performs the snapshot operation in a self-contained fashion, substantially independently, using hardware, firmware and/or software operating on the storage device itself. For instance, the storage device may perform snapshot operations generally without intervention or oversight from any of the other components of the system 100, e.g., a storage array may generate an “array-created” hardware snapshot and may also manage its storage, integrity, versioning, etc. In this manner, hardware snapshots can off-load other components of system 100 from snapshot processing. An array may receive a request from another component to take a snapshot and then proceed to execute the “hardware snapshot” operations autonomously, preferably reporting success to the requesting component.

A “software snapshot” (or “software-based snapshot”) operation, on the other hand, occurs where a component in system 100 (e.g., client computing device 102, etc.) implements a software layer that manages the snapshot operation via interaction with the target storage device. For instance, the component executing the snapshot management software layer may derive a set of pointers and/or data that represents the snapshot. The snapshot management software layer may then transmit the same to the target storage device, along with appropriate instructions for writing the snapshot. One example of a software snapshot product is Microsoft Volume Snapshot Service (VSS), which is part of the Microsoft Windows operating system.

Some types of snapshots do not actually create another physical copy of all the data as it existed at the particular point in time, but may simply create pointers that map files and directories to specific memory locations (e.g., to specific disk blocks) where the data resides as it existed at the particular point in time. For example, a snapshot copy may include a set of pointers derived from the file system or from an application. In some other cases, the snapshot may be created at the block-level, such that creation of the snapshot occurs without awareness of the file system. Each pointer points to a respective stored data block, so that collectively, the set of pointers reflect the storage location and state of the data object (e.g., file(s) or volume(s) or data set(s)) at the point in time when the snapshot copy was created.

An initial snapshot may use only a small amount of disk space needed to record a mapping or other data structure representing or otherwise tracking the blocks that correspond to the current state of the file system. Additional disk space is usually required only when files and directories change later on. Furthermore, when files change, typically only the pointers which map to blocks are copied, not the blocks themselves. For example for “copy-on-write” snapshots, when a block changes in primary storage, the block is copied to secondary storage or cached in primary storage before the block is overwritten in primary storage, and the pointer to that block is changed to reflect the new location of that block. The snapshot mapping of file system data may also be updated to reflect the changed block(s) at that particular point in time. In some other cases, a snapshot includes a full physical copy of all or substantially all of the data represented by the snapshot. Further examples of snapshot operations are provided in U.S. Pat. No. 7,529,782. A snapshot copy in many cases can be made quickly and without significantly impacting primary computing resources because large amounts of data need not be copied or moved. In some embodiments, a snapshot may exist as a virtual file system, parallel to the actual file system. Users in some cases gain read-only access to the record of files and directories of the snapshot. By electing to restore primary data 112 from a snapshot taken at a given point in time, users may also return the current file system to the state of the file system that existed when the snapshot was taken.

Replication Operations

Replication is another type of secondary copy operation. Some types of secondary copies 116 periodically capture images of primary data 112 at particular points in time (e.g., backups, archives, and snapshots). However, it can also be useful for recovery purposes to protect primary data 112 in a more continuous fashion, by replicating primary data 112 substantially as changes occur. In some cases a replication copy can be a mirror copy, for instance, where changes made to primary data 112 are mirrored or substantially immediately copied to another location (e.g., to secondary storage device(s) 108). By copying each write operation to the replication copy, two storage systems are kept synchronized or substantially synchronized so that they are virtually identical at approximately the same time. Where entire disk volumes are mirrored, however, mirroring can require significant amount of storage space and utilizes a large amount of processing resources.

According to some embodiments, secondary copy operations are performed on replicated data that represents a recoverable state, or “known good state” of a particular application running on the source system. For instance, in certain embodiments, known good replication copies may be viewed as copies of primary data 112. This feature allows the system to directly access, copy, restore, back up, or otherwise manipulate the replication copies as if they were the “live” primary data 112. This can reduce access time, storage utilization, and impact on source applications 110, among other benefits. Based on known good state information, system 100 can replicate sections of application data that represent a recoverable state rather than rote copying of blocks of data. Examples of replication operations (e.g., continuous data replication) are provided in U.S. Pat. No. 7,617,262.

Deduplication/Single-Instancing Operations

Deduplication or single-instance storage is useful to reduce the amount of non-primary data. For instance, some or all of the above-described secondary copy operations can involve deduplication in some fashion. New data is read, broken down into data portions of a selected granularity (e.g., sub-file level blocks, files, etc.), compared with corresponding portions that are already in secondary storage, and only new/changed portions are stored. Portions that already exist are represented as pointers to the already-stored data. Thus, a deduplicated secondary copy 116 may comprise actual data portions copied from primary data 112 and may further comprise pointers to already-stored data, which is generally more storage-efficient than a full copy.

In order to streamline the comparison process, system 100 may calculate and/or store signatures (e.g., hashes or cryptographically unique IDs) corresponding to the individual source data portions and compare the signatures to already-stored data signatures, instead of comparing entire data portions. In some cases, only a single instance of each data portion is stored, and deduplication operations may therefore be referred to interchangeably as “single-instancing” operations. Depending on the implementation, however, deduplication operations can store more than one instance of certain data portions, yet still significantly reduce stored-data redundancy. Depending on the embodiment, deduplication portions such as data blocks can be of fixed or variable length. Using variable length blocks can enhance deduplication by responding to changes in the data stream, but can involve more complex processing. In some cases, system 100 utilizes a technique for dynamically aligning deduplication blocks based on changing content in the data stream, as described in U.S. Pat. No. 8,364,652.

System 100 can deduplicate in a variety of manners at a variety of locations. For instance, in some embodiments, system 100 implements “target-side” deduplication by deduplicating data at the media agent 144 after being received from data agent 142. In some such cases, media agents 144 are generally configured to manage the deduplication process. For instance, one or more of the media agents 144 maintain a corresponding deduplication database that stores deduplication information (e.g., data block signatures). Examples of such a configuration are provided in U.S. Pat. No. 9,020,900. Instead of or in combination with “target-side” deduplication, “source-side” (or “client-side”) deduplication can also be performed, e.g., to reduce the amount of data to be transmitted by data agent 142 to media agent 144. Storage manager 140 may communicate with other components within system 100 via network protocols and cloud service provider APIs to facilitate cloud-based deduplication/single instancing, as exemplified in U.S. Pat. No. 8,954,446. Some other deduplication/single instancing techniques are described in U.S. Pat. Pub. No. 2006/0224846 and in U.S. Pat. No. 9,098,495.

Information Lifecycle Management and Hierarchical Storage Management

In some embodiments, files and other data over their lifetime move from more expensive quick-access storage to less expensive slower-access storage. Operations associated with moving data through various tiers of storage are sometimes referred to as information lifecycle management (ILM) operations.

One type of ILM operation is a hierarchical storage management (HSM) operation, which generally automatically moves data between classes of storage devices, such as from high-cost to low-cost storage devices. For instance, an HSM operation may involve movement of data from primary storage devices 104 to secondary storage devices 108, or between tiers of secondary storage devices 108. With each tier, the storage devices may be progressively cheaper, have relatively slower access/restore times, etc. For example, movement of data between tiers may occur as data becomes less important over time. In some embodiments, an HSM operation is similar to archiving in that creating an HSM copy may (though not always) involve deleting some of the source data, e.g., according to one or more criteria related to the source data. For example, an HSM copy may include primary data 112 or a secondary copy 116 that exceeds a given size threshold or a given age threshold. Often, and unlike some types of archive copies, HSM data that is removed or aged from the source is replaced by a logical reference pointer or stub. The reference pointer or stub can be stored in the primary storage device 104 or other source storage device, such as a secondary storage device 108 to replace the deleted source data and to point to or otherwise indicate the new location in (another) secondary storage device 108.

For example, files are generally moved between higher and lower cost storage depending on how often the files are accessed. When a user requests access to HSM data that has been removed or migrated, system 100 uses the stub to locate the data and can make recovery of the data appear transparent, even though the HSM data may be stored at a location different from other source data. In this manner, the data appears to the user (e.g., in file system browsing windows and the like) as if it still resides in the source location (e.g., in a primary storage device 104). The stub may include metadata associated with the corresponding data, so that a file system and/or application can provide some information about the data object and/or a limited-functionality version (e.g., a preview) of the data object.

An HSM copy may be stored in a format other than the native application format (e.g., compressed, encrypted, deduplicated, and/or otherwise modified). In some cases, copies which involve the removal of data from source storage and the maintenance of stub or other logical reference information on source storage may be referred to generally as “on-line archive copies.” On the other hand, copies which involve the removal of data from source storage without the maintenance of stub or other logical reference information on source storage may be referred to as “off-line archive copies.” Examples of HSM and ILM techniques are provided in U.S. Pat. No. 7,343,453.

Auxiliary Copy Operations

An auxiliary copy is generally a copy of an existing secondary copy 116. For instance, an initial secondary copy 116 may be derived from primary data 112 or from data residing in secondary storage subsystem 118, whereas an auxiliary copy is generated from the initial secondary copy 116. Auxiliary copies provide additional standby copies of data and may reside on different secondary storage devices 108 than the initial secondary copies 116. Thus, auxiliary copies can be used for recovery purposes if initial secondary copies 116 become unavailable. Exemplary auxiliary copy techniques are described in further detail in U.S. Pat. No. 8,230,195.

Disaster-Recovery Copy Operations

System 100 may also make and retain disaster recovery copies, often as secondary, high-availability disk copies. System 100 may create secondary copies and store them at disaster recovery locations using auxiliary copy or replication operations, such as continuous data replication technologies. Depending on the particular data protection goals, disaster recovery locations can be remote from the client computing devices 102 and primary storage devices 104, remote from some or all of the secondary storage devices 108, or both.

Data Manipulation, Including Encryption and Compression

Data manipulation and processing may include encryption and compression as well as integrity marking and checking, formatting for transmission, formatting for storage, etc. Data may be manipulated “client-side” by data agent 142 as well as “target-side” by media agent 144 in the course of creating secondary copy 116, or conversely in the course of restoring data from secondary to primary.

Encryption Operations

System 100 in some cases is configured to process data (e.g., files or other data objects, primary data 112, secondary copies 116, etc.), according to an appropriate encryption algorithm (e.g., Blowfish, Advanced Encryption Standard (AES), Triple Data Encryption Standard (3-DES), etc.) to limit access and provide data security. System 100 in some cases encrypts the data at the client level, such that client computing devices 102 (e.g., data agents 142) encrypt the data prior to transferring it to other components, e.g., before sending the data to media agents 144 during a secondary copy operation. In such cases, client computing device 102 may maintain or have access to an encryption key or passphrase for decrypting the data upon restore. Encryption can also occur when media agent 144 creates auxiliary copies or archive copies. Encryption may be applied in creating a secondary copy 116 of a previously unencrypted secondary copy 116, without limitation. In further embodiments, secondary storage devices 108 can implement built-in, high performance hardware-based encryption.

Compression Operations

Similar to encryption, system 100 may also or alternatively compress data in the course of generating a secondary copy 116. Compression encodes information such that fewer bits are needed to represent the information as compared to the original representation. Compression techniques are well known in the art. Compression operations may apply one or more data compression algorithms. Compression may be applied in creating a secondary copy 116 of a previously uncompressed secondary copy, e.g., when making archive copies or disaster recovery copies. The use of compression may result in metadata that specifies the nature of the compression, so that data may be uncompressed on restore if appropriate.

Data Analysis, Reporting, and Management Operations

Data analysis, reporting, and management operations can differ from data movement operations in that they do not necessarily involve copying, migration or other transfer of data between different locations in the system. For instance, data analysis operations may involve processing (e.g., offline processing) or modification of already stored primary data 112 and/or secondary copies 116. However, in some embodiments data analysis operations are performed in conjunction with data movement operations. Some data analysis operations include content indexing operations and classification operations which can be useful in leveraging data under management to enhance search and other features.

Classification Operations/Content Indexing

In some embodiments, information management system 100 analyzes and indexes characteristics, content, and metadata associated with primary data 112 (“online content indexing”) and/or secondary copies 116 (“off-line content indexing”). Content indexing can identify files or other data objects based on content (e.g., user-defined keywords or phrases, other keywords/phrases that are not defined by a user, etc.), and/or metadata (e.g., email metadata such as “to,” “from,” “cc,” “bcc,” attachment name, received time, etc.). Content indexes may be searched and search results may be restored.

System 100 generally organizes and catalogues the results into a content index, which may be stored within media agent database 152, for example. The content index can also include the storage locations of or pointer references to indexed data in primary data 112 and/or secondary copies 116. Results may also be stored elsewhere in system 100 (e.g., in primary storage device 104 or in secondary storage device 108). Such content index data provides storage manager 140 or other components with an efficient mechanism for locating primary data 112 and/or secondary copies 116 of data objects that match particular criteria, thus greatly increasing the search speed capability of system 100. For instance, search criteria can be specified by a user through user interface 158 of storage manager 140. Moreover, when system 100 analyzes data and/or metadata in secondary copies 116 to create an “off-line content index,” this operation has no significant impact on the performance of client computing devices 102 and thus does not take a toll on the production environment. Examples of content indexing techniques are provided in U.S. Pat. No. 8,170,995.

One or more components, such as a content index engine, can be configured to scan data and/or associated metadata for classification purposes to populate a database (or other data structure) of information, which can be referred to as a “data classification database” or a “metabase.” Depending on the embodiment, the data classification database(s) can be organized in a variety of different ways, including centralization, logical sub-divisions, and/or physical sub-divisions. For instance, one or more data classification databases may be associated with different subsystems or tiers within system 100. As an example, there may be a first metabase associated with primary storage subsystem 117 and a second metabase associated with secondary storage subsystem 118. In other cases, metabase(s) may be associated with individual components, e.g., client computing devices 102 and/or media agents 144. In some embodiments, a data classification database may reside as one or more data structures within management database 146, may be otherwise associated with storage manager 140, and/or may reside as a separate component. In some cases, metabase(s) may be included in separate database(s) and/or on separate storage device(s) from primary data 112 and/or secondary copies 116, such that operations related to the metabase(s) do not significantly impact performance on other components of system 100. In other cases, metabase(s) may be stored along with primary data 112 and/or secondary copies 116. Files or other data objects can be associated with identifiers (e.g., tag entries, etc.) to facilitate searches of stored data objects. Among a number of other benefits, the metabase can also allow efficient, automatic identification of files or other data objects to associate with secondary copy or other information management operations. For instance, a metabase can dramatically improve the speed with which system 100 can search through and identify data as compared to other approaches that involve scanning an entire file system. Examples of metabases and data classification operations are provided in U.S. Pat. Nos. 7,734,669 and 7,747,579.

Management and Reporting Operations

Certain embodiments leverage the integrated ubiquitous nature of system 100 to provide useful system-wide management and reporting. Operations management can generally include monitoring and managing the health and performance of system 100 by, without limitation, performing error tracking, generating granular storage/performance metrics (e.g., job success/failure information, deduplication efficiency, etc.), generating storage modeling and costing information, and the like. As an example, storage manager 140 or another component in system 100 may analyze traffic patterns and suggest and/or automatically route data to minimize congestion. In some embodiments, the system can generate predictions relating to storage operations or storage operation information. Such predictions, which may be based on a trending analysis, may predict various network operations or resource usage, such as network traffic levels, storage media use, use of bandwidth of communication links, use of media agent components, etc. Further examples of traffic analysis, trend analysis, prediction generation, and the like are described in U.S. Pat. No. 7,343,453.

In some configurations having a hierarchy of storage operation cells, a master storage manager 140 may track the status of subordinate cells, such as the status of jobs, system components, system resources, and other items, by communicating with storage managers 140 (or other components) in the respective storage operation cells. Moreover, the master storage manager 140 may also track status by receiving periodic status updates from the storage managers 140 (or other components) in the respective cells regarding jobs, system components, system resources, and other items. In some embodiments, a master storage manager 140 may store status information and other information regarding its associated storage operation cells and other system information in its management database 146 and/or index 150 (or in another location). The master storage manager 140 or other component may also determine whether certain storage-related or other criteria are satisfied, and may perform an action or trigger event (e.g., data migration) in response to the criteria being satisfied, such as where a storage threshold is met for a particular volume, or where inadequate protection exists for certain data. For instance, data from one or more storage operation cells is used to dynamically and automatically mitigate recognized risks, and/or to advise users of risks or suggest actions to mitigate these risks. For example, an information management policy may specify certain requirements (e.g., that a storage device should maintain a certain amount of free space, that secondary copies should occur at a particular interval, that data should be aged and migrated to other storage after a particular period, that data on a secondary volume should always have a certain level of availability and be restorable within a given time period, that data on a secondary volume may be mirrored or otherwise migrated to a specified number of other volumes, etc.). If a risk condition or other criterion is triggered, the system may notify the user of these conditions and may suggest (or automatically implement) a mitigation action to address the risk. For example, the system may indicate that data from a primary copy 112 should be migrated to a secondary storage device 108 to free up space on primary storage device 104. Examples of the use of risk factors and other triggering criteria are described in U.S. Pat. No. 7,343,453.

In some embodiments, system 100 may also determine whether a metric or other indication satisfies particular storage criteria sufficient to perform an action. For example, a storage policy or other definition might indicate that a storage manager 140 should initiate a particular action if a storage metric or other indication drops below or otherwise fails to satisfy specified criteria such as a threshold of data protection. In some embodiments, risk factors may be quantified into certain measurable service or risk levels. For example, certain applications and associated data may be considered to be more important relative to other data and services. Financial compliance data, for example, may be of greater importance than marketing materials, etc. Network administrators may assign priority values or “weights” to certain data and/or applications corresponding to the relative importance. The level of compliance of secondary copy operations specified for these applications may also be assigned a certain value. Thus, the health, impact, and overall importance of a service may be determined, such as by measuring the compliance value and calculating the product of the priority value and the compliance value to determine the “service level” and comparing it to certain operational thresholds to determine whether it is acceptable. Further examples of the service level determination are provided in U.S. Pat. No. 7,343,453.

System 100 may additionally calculate data costing and data availability associated with information management operation cells. For instance, data received from a cell may be used in conjunction with hardware-related information and other information about system elements to determine the cost of storage and/or the availability of particular data. Exemplary information generated could include how fast a particular department is using up available storage space, how long data would take to recover over a particular pathway from a particular secondary storage device, costs over time, etc. Moreover, in some embodiments, such information may be used to determine or predict the overall cost associated with the storage of certain information. The cost associated with hosting a certain application may be based, at least in part, on the type of media on which the data resides, for example. Storage devices may be assigned to a particular cost categories, for example. Further examples of costing techniques are described in U.S. Pat. No. 7,343,453.

Any of the above types of information (e.g., information related to trending, predictions, job, cell or component status, risk, service level, costing, etc.) can generally be provided to users via user interface 158 in a single integrated view or console (not shown). Report types may include: scheduling, event management, media management and data aging. Available reports may also include backup history, data aging history, auxiliary copy history, job history, library and drive, media in library, restore history, and storage policy, etc., without limitation. Such reports may be specified and created at a certain point in time as a system analysis, forecasting, or provisioning tool. Integrated reports may also be generated that illustrate storage and performance metrics, risks and storage costing information. Moreover, users may create their own reports based on specific needs. User interface 158 can include an option to graphically depict the various components in the system using appropriate icons. As one example, user interface 158 may provide a graphical depiction of primary storage devices 104, secondary storage devices 108, data agents 142 and/or media agents 144, and their relationship to one another in system 100.

In general, the operations management functionality of system 100 can facilitate planning and decision-making. For example, in some embodiments, a user may view the status of some or all jobs as well as the status of each component of information management system 100. Users may then plan and make decisions based on this data. For instance, a user may view high-level information regarding secondary copy operations for system 100, such as job status, component status, resource status (e.g., communication pathways, etc.), and other information. The user may also drill down or use other means to obtain more detailed information regarding a particular component, job, or the like. Further examples are provided in U.S. Pat. No. 7,343,453.

System 100 can also be configured to perform system-wide e-discovery operations in some embodiments. In general, e-discovery operations provide a unified collection and search capability for data in the system, such as data stored in secondary storage devices 108 (e.g., backups, archives, or other secondary copies 116). For example, system 100 may construct and maintain a virtual repository for data stored in system 100 that is integrated across source applications 110, different storage device types, etc. According to some embodiments, e-discovery utilizes other techniques described herein, such as data classification and/or content indexing.

Information Management Policies

An information management policy 148 can include a data structure or other information source that specifies a set of parameters (e.g., criteria and rules) associated with secondary copy and/or other information management operations.

One type of information management policy 148 is a “storage policy.” According to certain embodiments, a storage policy generally comprises a data structure or other information source that defines (or includes information sufficient to determine) a set of preferences or other criteria for performing information management operations. Storage policies can include one or more of the following: (1) what data will be associated with the storage policy, e.g., subclient; (2) a destination to which the data will be stored; (3) datapath information specifying how the data will be communicated to the destination; (4) the type of secondary copy operation to be performed; and (5) retention information specifying how long the data will be retained at the destination (see, e.g., FIG. 1E). Data associated with a storage policy can be logically organized into subclients, which may represent primary data 112 and/or secondary copies 116. A subclient may represent static or dynamic associations of portions of a data volume. Subclients may represent mutually exclusive portions. Thus, in certain embodiments, a portion of data may be given a label and the association is stored as a static entity in an index, database or other storage location. Subclients may also be used as an effective administrative scheme of organizing data according to data type, department within the enterprise, storage preferences, or the like. Depending on the configuration, subclients can correspond to files, folders, virtual machines, databases, etc. In one exemplary scenario, an administrator may find it preferable to separate e-mail data from financial data using two different subclients.

A storage policy can define where data is stored by specifying a target or destination storage device (or group of storage devices). For instance, where the secondary storage device 108 includes a group of disk libraries, the storage policy may specify a particular disk library for storing the subclients associated with the policy. As another example, where the secondary storage devices 108 include one or more tape libraries, the storage policy may specify a particular tape library for storing the subclients associated with the storage policy, and may also specify a drive pool and a tape pool defining a group of tape drives and a group of tapes, respectively, for use in storing the subclient data. While information in the storage policy can be statically assigned in some cases, some or all of the information in the storage policy can also be dynamically determined based on criteria set forth in the storage policy. For instance, based on such criteria, a particular destination storage device(s) or other parameter of the storage policy may be determined based on characteristics associated with the data involved in a particular secondary copy operation, device availability (e.g., availability of a secondary storage device 108 or a media agent 144), network status and conditions (e.g., identified bottlenecks), user credentials, and the like.

Datapath information can also be included in the storage policy. For instance, the storage policy may specify network pathways and components to utilize when moving the data to the destination storage device(s). In some embodiments, the storage policy specifies one or more media agents 144 for conveying data associated with the storage policy between the source and destination. A storage policy can also specify the type(s) of associated operations, such as backup, archive, snapshot, auxiliary copy, or the like. Furthermore, retention parameters can specify how long the resulting secondary copies 116 will be kept (e.g., a number of days, months, years, etc.), perhaps depending on organizational needs and/or compliance criteria.

When adding a new client computing device 102, administrators can manually configure information management policies 148 and/or other settings, e.g., via user interface 158. However, this can be an involved process resulting in delays, and it may be desirable to begin data protection operations quickly, without awaiting human intervention. Thus, in some embodiments, system 100 automatically applies a default configuration to client computing device 102. As one example, when one or more data agent(s) 142 are installed on a client computing device 102, the installation script may register the client computing device 102 with storage manager 140, which in turn applies the default configuration to the new client computing device 102. In this manner, data protection operations can begin substantially immediately. The default configuration can include a default storage policy, for example, and can specify any appropriate information sufficient to begin data protection operations. This can include a type of data protection operation, scheduling information, a target secondary storage device 108, data path information (e.g., a particular media agent 144), and the like.

Another type of information management policy 148 is a “scheduling policy,” which specifies when and how often to perform operations. Scheduling parameters may specify with what frequency (e.g., hourly, weekly, daily, event-based, etc.) or under what triggering conditions secondary copy or other information management operations are to take place. Scheduling policies in some cases are associated with particular components, such as a subclient, client computing device 102, and the like.

Another type of information management policy 148 is an “audit policy” (or “security policy”), which comprises preferences, rules and/or criteria that protect sensitive data in system 100. For example, an audit policy may define “sensitive objects” which are files or data objects that contain particular keywords (e.g., “confidential,” or “privileged”) and/or are associated with particular keywords (e.g., in metadata) or particular flags (e.g., in metadata identifying a document or email as personal, confidential, etc.). An audit policy may further specify rules for handling sensitive objects. As an example, an audit policy may require that a reviewer approve the transfer of any sensitive objects to a cloud storage site, and that if approval is denied for a particular sensitive object, the sensitive object should be transferred to a local primary storage device 104 instead. To facilitate this approval, the audit policy may further specify how a secondary storage computing device 106 or other system component should notify a reviewer that a sensitive object is slated for transfer.

Another type of information management policy 148 is a “provisioning policy,” which can include preferences, priorities, rules, and/or criteria that specify how client computing devices 102 (or groups thereof) may utilize system resources, such as available storage on cloud storage and/or network bandwidth. A provisioning policy specifies, for example, data quotas for particular client computing devices 102 (e.g., a number of gigabytes that can be stored monthly, quarterly or annually). Storage manager 140 or other components may enforce the provisioning policy. For instance, media agents 144 may enforce the policy when transferring data to secondary storage devices 108. If a client computing device 102 exceeds a quota, a budget for the client computing device 102 (or associated department) may be adjusted accordingly or an alert may trigger.

While the above types of information management policies 148 are described as separate policies, one or more of these can be generally combined into a single information management policy 148. For instance, a storage policy may also include or otherwise be associated with one or more scheduling, audit, or provisioning policies or operational parameters thereof. Moreover, while storage policies are typically associated with moving and storing data, other policies may be associated with other types of information management operations. The following is a non-exhaustive list of items that information management policies 148 may specify:

-   -   schedules or other timing information, e.g., specifying when         and/or how often to perform information management operations;     -   the type of secondary copy 116 and/or copy format (e.g.,         snapshot, backup, archive, HSM, etc.);     -   a location or a class or quality of storage for storing         secondary copies 116 (e.g., one or more particular secondary         storage devices 108);     -   preferences regarding whether and how to encrypt, compress,         deduplicate, or otherwise modify or transform secondary copies         116;     -   which system components and/or network pathways (e.g., preferred         media agents 144) should be used to perform secondary storage         operations;     -   resource allocation among different computing devices or other         system components used in performing information management         operations (e.g., bandwidth allocation, available storage         capacity, etc.);     -   whether and how to synchronize or otherwise distribute files or         other data objects across multiple computing devices or hosted         services; and     -   retention information specifying the length of time primary data         112 and/or secondary copies 116 should be retained, e.g., in a         particular class or tier of storage devices, or within the         system 100.

Information management policies 148 can additionally specify or depend on historical or current criteria that may be used to determine which rules to apply to a particular data object, system component, or information management operation, such as:

-   -   frequency with which primary data 112 or a secondary copy 116 of         a data object or metadata has been or is predicted to be used,         accessed, or modified;     -   time-related factors (e.g., aging information such as time since         the creation or modification of a data object);     -   deduplication information (e.g., hashes, data blocks,         deduplication block size, deduplication efficiency or other         metrics);     -   an estimated or historic usage or cost associated with different         components (e.g., with secondary storage devices 108);     -   the identity of users, applications 110, client computing         devices 102 and/or other computing devices that created,         accessed, modified, or otherwise utilized primary data 112 or         secondary copies 116;     -   a relative sensitivity (e.g., confidentiality, importance) of a         data object, e.g., as determined by its content and/or metadata;     -   the current or historical storage capacity of various storage         devices;     -   the current or historical network capacity of network pathways         connecting various components within the storage operation cell;     -   access control lists or other security information; and the         content of a particular data object (e.g., its textual content)         or of metadata associated with the data object.

Exemplary Storage Policy and Secondary Copy Operations

FIG. 1E includes a data flow diagram depicting performance of secondary copy operations by an embodiment of information management system 100, according to an exemplary storage policy 148A. System 100 includes a storage manager 140, a client computing device 102 having a file system data agent 142A and an email data agent 142B operating thereon, a primary storage device 104, two media agents 144A, 144B, and two secondary storage devices 108: a disk library 108A and a tape library 108B. As shown, primary storage device 104 includes primary data 112A, which is associated with a logical grouping of data associated with a file system (“file system subclient”), and primary data 112B, which is a logical grouping of data associated with email (“email subclient”). The techniques described with respect to FIG. 1E can be utilized in conjunction with data that is otherwise organized as well.

As indicated by the dashed box, the second media agent 144B and tape library 108B are “off-site,” and may be remotely located from the other components in system 100 (e.g., in a different city, office building, etc.). Indeed, “off-site” may refer to a magnetic tape located in remote storage, which must be manually retrieved and loaded into a tape drive to be read. In this manner, information stored on the tape library 108B may provide protection in the event of a disaster or other failure at the main site(s) where data is stored.

The file system subclient 112A in certain embodiments generally comprises information generated by the file system and/or operating system of client computing device 102, and can include, for example, file system data (e.g., regular files, file tables, mount points, etc.), operating system data (e.g., registries, event logs, etc.), and the like. The e-mail subclient 112B can include data generated by an e-mail application operating on client computing device 102, e.g., mailbox information, folder information, emails, attachments, associated database information, and the like. As described above, the subclients can be logical containers, and the data included in the corresponding primary data 112A and 112B may or may not be stored contiguously.

The exemplary storage policy 148A includes backup copy preferences or rule set 160, disaster recovery copy preferences or rule set 162, and compliance copy preferences or rule set 164. Backup copy rule set 160 specifies that it is associated with file system subclient 166 and email subclient 168. Each of subclients 166 and 168 are associated with the particular client computing device 102. Backup copy rule set 160 further specifies that the backup operation will be written to disk library 108A and designates a particular media agent 144A to convey the data to disk library 108A. Finally, backup copy rule set 160 specifies that backup copies created according to rule set 160 are scheduled to be generated hourly and are to be retained for 30 days. In some other embodiments, scheduling information is not included in storage policy 148A and is instead specified by a separate scheduling policy.

Disaster recovery copy rule set 162 is associated with the same two subclients 166 and 168. However, disaster recovery copy rule set 162 is associated with tape library 108B, unlike backup copy rule set 160. Moreover, disaster recovery copy rule set 162 specifies that a different media agent, namely 144B, will convey data to tape library 108B. Disaster recovery copies created according to rule set 162 will be retained for 60 days and will be generated daily. Disaster recovery copies generated according to disaster recovery copy rule set 162 can provide protection in the event of a disaster or other catastrophic data loss that would affect the backup copy 116A maintained on disk library 108A.

Compliance copy rule set 164 is only associated with the email subclient 168, and not the file system subclient 166. Compliance copies generated according to compliance copy rule set 164 will therefore not include primary data 112A from the file system subclient 166. For instance, the organization may be under an obligation to store and maintain copies of email data for a particular period of time (e.g., 10 years) to comply with state or federal regulations, while similar regulations do not apply to file system data. Compliance copy rule set 164 is associated with the same tape library 108B and media agent 144B as disaster recovery copy rule set 162, although a different storage device or media agent could be used in other embodiments. Finally, compliance copy rule set 164 specifies that the copies it governs will be generated quarterly and retained for 10 years.

Secondary Copy Jobs

A logical grouping of secondary copy operations governed by a rule set and being initiated at a point in time may be referred to as a “secondary copy job” (and sometimes may be called a “backup job,” even though it is not necessarily limited to creating only backup copies). Secondary copy jobs may be initiated on demand as well. Steps 1-9 below illustrate three secondary copy jobs based on storage policy 148A.

Referring to FIG. 1E, at step 1, storage manager 140 initiates a backup job according to the backup copy rule set 160, which logically comprises all the secondary copy operations necessary to effectuate rules 160 in storage policy 148A every hour, including steps 1-4 occurring hourly. For instance, a scheduling service running on storage manager 140 accesses backup copy rule set 160 or a separate scheduling policy associated with client computing device 102 and initiates a backup job on an hourly basis. Thus, at the scheduled time, storage manager 140 sends instructions to client computing device 102 (i.e., to both data agent 142A and data agent 142B) to begin the backup job.

At step 2, file system data agent 142A and email data agent 142B on client computing device 102 respond to instructions from storage manager 140 by accessing and processing the respective subclient primary data 112A and 112B involved in the backup copy operation, which can be found in primary storage device 104. Because the secondary copy operation is a backup copy operation, the data agent(s) 142A, 142B may format the data into a backup format or otherwise process the data suitable for a backup copy.

At step 3, client computing device 102 communicates the processed file system data (e.g., using file system data agent 142A) and the processed email data (e.g., using email data agent 142B) to the first media agent 144A according to backup copy rule set 160, as directed by storage manager 140. Storage manager 140 may further keep a record in management database 146 of the association between media agent 144A and one or more of: client computing device 102, file system subclient 112A, file system data agent 142A, email subclient 112B, email data agent 142B, and/or backup copy 116A.

The target media agent 144A receives the data-agent-processed data from client computing device 102, and at step 4 generates and conveys backup copy 116A to disk library 108A to be stored as backup copy 116A, again at the direction of storage manager 140 and according to backup copy rule set 160. Media agent 144A can also update its index 153 to include data and/or metadata related to backup copy 116A, such as information indicating where the backup copy 116A resides on disk library 108A, where the email copy resides, where the file system copy resides, data and metadata for cache retrieval, etc. Storage manager 140 may similarly update its index 150 to include information relating to the secondary copy operation, such as information relating to the type of operation, a physical location associated with one or more copies created by the operation, the time the operation was performed, status information relating to the operation, the components involved in the operation, and the like. In some cases, storage manager 140 may update its index 150 to include some or all of the information stored in index 153 of media agent 144A. At this point, the backup job may be considered complete. After the 30-day retention period expires, storage manager 140 instructs media agent 144A to delete backup copy 116A from disk library 108A and indexes 150 and/or 153 are updated accordingly.

At step 5, storage manager 140 initiates another backup job for a disaster recovery copy according to the disaster recovery rule set 162. Illustratively this includes steps 5-7 occurring daily for creating disaster recovery copy 1168. Illustratively, and by way of illustrating the scalable aspects and off-loading principles embedded in system 100, disaster recovery copy 1168 is based on backup copy 116A and not on primary data 112A and 1128.

At step 6, illustratively based on instructions received from storage manager 140 at step 5, the specified media agent 1448 retrieves the most recent backup copy 116A from disk library 108A.

At step 7, again at the direction of storage manager 140 and as specified in disaster recovery copy rule set 162, media agent 144B uses the retrieved data to create a disaster recovery copy 1168 and store it to tape library 1088. In some cases, disaster recovery copy 1168 is a direct, mirror copy of backup copy 116A, and remains in the backup format. In other embodiments, disaster recovery copy 1168 may be further compressed or encrypted, or may be generated in some other manner, such as by using primary data 112A and 1128 from primary storage device 104 as sources. The disaster recovery copy operation is initiated once a day and disaster recovery copies 1168 are deleted after 60 days; indexes 153 and/or 150 are updated accordingly when/after each information management operation is executed and/or completed. The present backup job may be considered completed.

At step 8, storage manager 140 initiates another backup job according to compliance rule set 164, which performs steps 8-9 quarterly to create compliance copy 116C. For instance, storage manager 140 instructs media agent 144B to create compliance copy 116C on tape library 1088, as specified in the compliance copy rule set 164.

At step 9 in the example, compliance copy 116C is generated using disaster recovery copy 1168 as the source. This is efficient, because disaster recovery copy resides on the same secondary storage device and thus no network resources are required to move the data. In other embodiments, compliance copy 116C is instead generated using primary data 1128 corresponding to the email subclient or using backup copy 116A from disk library 108A as source data. As specified in the illustrated example, compliance copies 116C are created quarterly, and are deleted after ten years, and indexes 153 and/or 150 are kept up-to-date accordingly.

Exemplary Applications of Storage Policies—Information Governance Policies and Classification

Again referring to FIG. 1E, storage manager 140 may permit a user to specify aspects of storage policy 148A. For example, the storage policy can be modified to include information governance policies to define how data should be managed in order to comply with a certain regulation or business objective. The various policies may be stored, for example, in management database 146. An information governance policy may align with one or more compliance tasks that are imposed by regulations or business requirements. Examples of information governance policies might include a Sarbanes-Oxley policy, a HIPAA policy, an electronic discovery (e-discovery) policy, and so on.

Information governance policies allow administrators to obtain different perspectives on an organization's online and offline data, without the need for a dedicated data silo created solely for each different viewpoint. As described previously, the data storage systems herein build an index that reflects the contents of a distributed data set that spans numerous clients and storage devices, including both primary data and secondary copies, and online and offline copies. An organization may apply multiple information governance policies in a top-down manner over that unified data set and indexing schema in order to view and manipulate the data set through different lenses, each of which is adapted to a particular compliance or business goal. Thus, for example, by applying an e-discovery policy and a Sarbanes-Oxley policy, two different groups of users in an organization can conduct two very different analyses of the same underlying physical set of data/copies, which may be distributed throughout the information management system.

An information governance policy may comprise a classification policy, which defines a taxonomy of classification terms or tags relevant to a compliance task and/or business objective. A classification policy may also associate a defined tag with a classification rule. A classification rule defines a particular combination of criteria, such as users who have created, accessed or modified a document or data object; file or application types; content or metadata keywords; clients or storage locations; dates of data creation and/or access; review status or other status within a workflow (e.g., reviewed or un-reviewed); modification times or types of modifications; and/or any other data attributes in any combination, without limitation. A classification rule may also be defined using other classification tags in the taxonomy. The various criteria used to define a classification rule may be combined in any suitable fashion, for example, via Boolean operators, to define a complex classification rule. As an example, an e-discovery classification policy might define a classification tag “privileged” that is associated with documents or data objects that (1) were created or modified by legal department staff, or (2) were sent to or received from outside counsel via email, or (3) contain one of the following keywords: “privileged” or “attorney” or “counsel,” or other like terms. Accordingly, all these documents or data objects will be classified as “privileged.”

One specific type of classification tag, which may be added to an index at the time of indexing, is an “entity tag.” An entity tag may be, for example, any content that matches a defined data mask format. Examples of entity tags might include, e.g., social security numbers (e.g., any numerical content matching the formatting mask XXX-XX-XXXX), credit card numbers (e.g., content having a 13-16 digit string of numbers), SKU numbers, product numbers, etc. A user may define a classification policy by indicating criteria, parameters or descriptors of the policy via a graphical user interface, such as a form or page with fields to be filled in, pull-down menus or entries allowing one or more of several options to be selected, buttons, sliders, hypertext links or other known user interface tools for receiving user input, etc. For example, a user may define certain entity tags, such as a particular product number or project ID. In some implementations, the classification policy can be implemented using cloud-based techniques. For example, the storage devices may be cloud storage devices, and the storage manager 140 may execute cloud service provider API over a network to classify data stored on cloud storage devices.

Restore Operations from Secondary Copies

While not shown in FIG. 1E, at some later point in time, a restore operation can be initiated involving one or more of secondary copies 116A, 116B, and 116C. A restore operation logically takes a selected secondary copy 116, reverses the effects of the secondary copy operation that created it, and stores the restored data to primary storage where a client computing device 102 may properly access it as primary data. A media agent 144 and an appropriate data agent 142 (e.g., executing on the client computing device 102) perform the tasks needed to complete a restore operation. For example, data that was encrypted, compressed, and/or deduplicated in the creation of secondary copy 116 will be correspondingly rehydrated (reversing deduplication), uncompressed, and unencrypted into a format appropriate to primary data. Metadata stored within or associated with the secondary copy 116 may be used during the restore operation. In general, restored data should be indistinguishable from other primary data 112. Preferably, the restored data has fully regained the native format that may make it immediately usable by application 110.

As one example, a user may manually initiate a restore of backup copy 116A, e.g., by interacting with user interface 158 of storage manager 140 or with a web-based console with access to system 100. Storage manager 140 may accesses data in its index 150 and/or management database 146 (and/or the respective storage policy 148A) associated with the selected backup copy 116A to identify the appropriate media agent 144A and/or secondary storage device 108A where the secondary copy resides. The user may be presented with a representation (e.g., stub, thumbnail, listing, etc.) and metadata about the selected secondary copy, in order to determine whether this is the appropriate copy to be restored, e.g., date that the original primary data was created. Storage manager 140 will then instruct media agent 144A and an appropriate data agent 142 on the target client computing device 102 to restore secondary copy 116A to primary storage device 104. A media agent may be selected for use in the restore operation based on a load balancing algorithm, an availability based algorithm, or other criteria. The selected media agent, e.g., 144A, retrieves secondary copy 116A from disk library 108A. For instance, media agent 144A may access its index 153 to identify a location of backup copy 116A on disk library 108A, or may access location information residing on disk library 108A itself.

In some cases a backup copy 116A that was recently created or accessed, may be cached to speed up the restore operation. In such a case, media agent 144A accesses a cached version of backup copy 116A residing in index 153, without having to access disk library 108A for some or all of the data. Once it has retrieved backup copy 116A, the media agent 144A communicates the data to the requesting client computing device 102. Upon receipt, file system data agent 142A and email data agent 142B may unpack (e.g., restore from a backup format to the native application format) the data in backup copy 116A and restore the unpackaged data to primary storage device 104. In general, secondary copies 116 may be restored to the same volume or folder in primary storage device 104 from which the secondary copy was derived; to another storage location or client computing device 102; to shared storage, etc. In some cases, the data may be restored so that it may be used by an application 110 of a different version/vintage from the application that created the original primary data 112.

Exemplary Secondary Copy Formatting

The formatting and structure of secondary copies 116 can vary depending on the embodiment. In some cases, secondary copies 116 are formatted as a series of logical data units or “chunks” (e.g., 512 MB, 1 GB, 2 GB, 4 GB, or 8 GB chunks). This can facilitate efficient communication and writing to secondary storage devices 108, e.g., according to resource availability. For example, a single secondary copy 116 may be written on a chunk-by-chunk basis to one or more secondary storage devices 108. In some cases, users can select different chunk sizes, e.g., to improve throughput to tape storage devices. Generally, each chunk can include a header and a payload. The payload can include files (or other data units) or subsets thereof included in the chunk, whereas the chunk header generally includes metadata relating to the chunk, some or all of which may be derived from the payload. For example, during a secondary copy operation, media agent 144, storage manager 140, or other component may divide files into chunks and generate headers for each chunk by processing the files. Headers can include a variety of information such as file and/or volume identifier(s), offset(s), and/or other information associated with the payload data items, a chunk sequence number, etc. Importantly, in addition to being stored with secondary copy 116 on secondary storage device 108, chunk headers can also be stored to index 153 of the associated media agent(s) 144 and/or to index 150 associated with storage manager 140. This can be useful for providing faster processing of secondary copies 116 during browsing, restores, or other operations. In some cases, once a chunk is successfully transferred to a secondary storage device 108, the secondary storage device 108 returns an indication of receipt, e.g., to media agent 144 and/or storage manager 140, which may update their respective indexes 153, 150 accordingly. During restore, chunks may be processed (e.g., by media agent 144) according to the information in the chunk header to reassemble the files.

Data can also be communicated within system 100 in data channels that connect client computing devices 102 to secondary storage devices 108. These data channels can be referred to as “data streams,” and multiple data streams can be employed to parallelize an information management operation, improving data transfer rate, among other advantages. Example data formatting techniques including techniques involving data streaming, chunking, and the use of other data structures in creating secondary copies are described in U.S. Pat. Nos. 7,315,923, 8,156,086, and 8,578,120.

FIGS. 1F and 1G are diagrams of example data streams 170 and 171, respectively, which may be employed for performing information management operations. Referring to FIG. 1F, data agent 142 forms data stream 170 from source data associated with a client computing device 102 (e.g., primary data 112). Data stream 170 is composed of multiple pairs of stream header 172 and stream data (or stream payload) 174. Data streams 170 and 171 shown in the illustrated example are for a single-instanced storage operation, and a stream payload 174 therefore may include both single-instance (SI) data and/or non-SI data. A stream header 172 includes metadata about the stream payload 174. This metadata may include, for example, a length of the stream payload 174, an indication of whether the stream payload 174 is encrypted, an indication of whether the stream payload 174 is compressed, an archive file identifier (ID), an indication of whether the stream payload 174 is single instanceable, and an indication of whether the stream payload 174 is a start of a block of data.

Referring to FIG. 1G, data stream 171 has the stream header 172 and stream payload 174 aligned into multiple data blocks. In this example, the data blocks are of size 64 KB. The first two stream header 172 and stream payload 174 pairs comprise a first data block of size 64 KB. The first stream header 172 indicates that the length of the succeeding stream payload 174 is 63 KB and that it is the start of a data block. The next stream header 172 indicates that the succeeding stream payload 174 has a length of 1 KB and that it is not the start of a new data block. Immediately following stream payload 174 is a pair comprising an identifier header 176 and identifier data 178. The identifier header 176 includes an indication that the succeeding identifier data 178 includes the identifier for the immediately previous data block. The identifier data 178 includes the identifier that the data agent 142 generated for the data block. The data stream 171 also includes other stream header 172 and stream payload 174 pairs, which may be for SI data and/or non-SI data.

FIG. 1H is a diagram illustrating data structures 180 that may be used to store blocks of SI data and non-SI data on a storage device (e.g., secondary storage device 108). According to certain embodiments, data structures 180 do not form part of a native file system of the storage device. Data structures 180 include one or more volume folders 182, one or more chunk folders 184/185 within the volume folder 182, and multiple files within chunk folder 184. Each chunk folder 184/185 includes a metadata file 186/187, a metadata index file 188/189, one or more container files 190/191/193, and a container index file 192/194. Metadata file 186/187 stores non-SI data blocks as well as links to SI data blocks stored in container files. Metadata index file 188/189 stores an index to the data in the metadata file 186/187. Container files 190/191/193 store SI data blocks. Container index file 192/194 stores an index to container files 190/191/193. Among other things, container index file 192/194 stores an indication of whether a corresponding block in a container file 190/191/193 is referred to by a link in a metadata file 186/187. For example, data block B2 in the container file 190 is referred to by a link in metadata file 187 in chunk folder 185. Accordingly, the corresponding index entry in container index file 192 indicates that data block B2 in container file 190 is referred to. As another example, data block B1 in container file 191 is referred to by a link in metadata file 187, and so the corresponding index entry in container index file 192 indicates that this data block is referred to.

As an example, data structures 180 illustrated in FIG. 1H may have been created as a result of separate secondary copy operations involving two client computing devices 102. For example, a first secondary copy operation on a first client computing device 102 could result in the creation of the first chunk folder 184, and a second secondary copy operation on a second client computing device 102 could result in the creation of the second chunk folder 185. Container files 190/191 in the first chunk folder 184 would contain the blocks of SI data of the first client computing device 102. If the two client computing devices 102 have substantially similar data, the second secondary copy operation on the data of the second client computing device 102 would result in media agent 144 storing primarily links to the data blocks of the first client computing device 102 that are already stored in the container files 190/191. Accordingly, while a first secondary copy operation may result in storing nearly all of the data subject to the operation, subsequent secondary storage operations involving similar data may result in substantial data storage space savings, because links to already stored data blocks can be stored instead of additional instances of data blocks.

If the operating system of the secondary storage computing device 106 on which media agent 144 operates supports sparse files, then when media agent 144 creates container files 190/191/193, it can create them as sparse files. A sparse file is a type of file that may include empty space (e.g., a sparse file may have real data within it, such as at the beginning of the file and/or at the end of the file, but may also have empty space in it that is not storing actual data, such as a contiguous range of bytes all having a value of zero). Having container files 190/191/193 be sparse files allows media agent 144 to free up space in container files 190/191/193 when blocks of data in container files 190/191/193 no longer need to be stored on the storage devices. In some examples, media agent 144 creates a new container file 190/191/193 when a container file 190/191/193 either includes 100 blocks of data or when the size of the container file 190 exceeds 50 MB. In other examples, media agent 144 creates a new container file 190/191/193 when a container file 190/191/193 satisfies other criteria (e.g., it contains from approx. 100 to approx. 1000 blocks or when its size exceeds approximately 50 MB to 1 GB). In some cases, a file on which a secondary copy operation is performed may comprise a large number of data blocks. For example, a 100 MB file may comprise 400 data blocks of size 256 KB. If such a file is to be stored, its data blocks may span more than one container file, or even more than one chunk folder. As another example, a database file of 20 GB may comprise over 40,000 data blocks of size 512 KB. If such a database file is to be stored, its data blocks will likely span multiple container files, multiple chunk folders, and potentially multiple volume folders. Restoring such files may require accessing multiple container files, chunk folders, and/or volume folders to obtain the requisite data blocks.

Using Backup Data for Replication and Disaster Recovery (“Live Synchronization”)

There is an increased demand to off-load resource intensive information management tasks (e.g., data replication tasks) away from production devices (e.g., physical or virtual client computing devices) in order to maximize production efficiency. At the same time, enterprises expect access to readily-available up-to-date recovery copies in the event of failure, with little or no production downtime.

FIG. 2A illustrates a system 200 configured to address these and other issues by using backup or other secondary copy data to synchronize a source subsystem 201 (e.g., a production site) with a destination subsystem 203 (e.g., a failover site). Such a technique can be referred to as “live synchronization” and/or “live synchronization replication.” In the illustrated embodiment, the source client computing devices 202 a include one or more virtual machines (or “VMs”) executing on one or more corresponding VM host computers 205 a, though the source need not be virtualized. The destination site 203 may be at a location that is remote from the production site 201, or may be located in the same data center, without limitation. One or more of the production site 201 and destination site 203 may reside at data centers at known geographic locations, or alternatively may operate “in the cloud.”

The synchronization can be achieved by generally applying an ongoing stream of incremental backups from the source subsystem 201 to the destination subsystem 203, such as according to what can be referred to as an “incremental forever” approach. FIG. 2A illustrates an embodiment of a data flow which may be orchestrated at the direction of one or more storage managers (not shown). At step 1, the source data agent(s) 242 a and source media agent(s) 244 a work together to write backup or other secondary copies of the primary data generated by the source client computing devices 202 a into the source secondary storage device(s) 208 a. At step 2, the backup/secondary copies are retrieved by the source media agent(s) 244 a from secondary storage. At step 3, source media agent(s) 244 a communicate the backup/secondary copies across a network to the destination media agent(s) 244 b in destination subsystem 203.

As shown, the data can be copied from source to destination in an incremental fashion, such that only changed blocks are transmitted, and in some cases multiple incremental backups are consolidated at the source so that only the most current changed blocks are transmitted to and applied at the destination. An example of live synchronization of virtual machines using the “incremental forever” approach is found in U.S. Patent Application No. 62/265,339 entitled “Live Synchronization and Management of Virtual Machines across Computing and Virtualization Platforms and Using Live Synchronization to Support Disaster Recovery.” Moreover, a deduplicated copy can be employed to further reduce network traffic from source to destination. For instance, the system can utilize the deduplicated copy techniques described in U.S. Pat. No. 9,239,687, entitled “Systems and Methods for Retaining and Using Data Block Signatures in Data Protection Operations.”

At step 4, destination media agent(s) 244 b write the received backup/secondary copy data to the destination secondary storage device(s) 208 b. At step 5, the synchronization is completed when the destination media agent(s) and destination data agent(s) 242 b restore the backup/secondary copy data to the destination client computing device(s) 202 b. The destination client computing device(s) 202 b may be kept “warm” awaiting activation in case failure is detected at the source. This synchronization/replication process can incorporate the techniques described in U.S. patent application Ser. No. 14/721,971, entitled “Replication Using Deduplicated Secondary Copy Data.”

Where the incremental backups are applied on a frequent, on-going basis, the synchronized copies can be viewed as mirror or replication copies. Moreover, by applying the incremental backups to the destination site 203 using backup or other secondary copy data, the production site 201 is not burdened with the synchronization operations. Because the destination site 203 can be maintained in a synchronized “warm” state, the downtime for switching over from the production site 201 to the destination site 203 is substantially less than with a typical restore from secondary storage. Thus, the production site 201 may flexibly and efficiently fail over, with minimal downtime and with relatively up-to-date data, to a destination site 203, such as a cloud-based failover site. The destination site 203 can later be reverse synchronized back to the production site 201, such as after repairs have been implemented or after the failure has passed.

Integrating With the Cloud Using File System Protocols

Given the ubiquity of cloud computing, it can be increasingly useful to provide data protection and other information management services in a scalable, transparent, and highly plug-able fashion. FIG. 2B illustrates an information management system 200 having an architecture that provides such advantages, and incorporates use of a standard file system protocol between primary and secondary storage subsystems 217, 218. As shown, the use of the network file system (NFS) protocol (or any another appropriate file system protocol such as that of the Common Internet File System (CIFS)) allows data agent 242 to be moved from the primary storage subsystem 217 to the secondary storage subsystem 218. For instance, as indicated by the dashed box 206 around data agent 242 and media agent 244, data agent 242 can co-reside with media agent 244 on the same server (e.g., a secondary storage computing device such as component 106), or in some other location in secondary storage subsystem 218.

Where NFS is used, for example, secondary storage subsystem 218 allocates an NFS network path to the client computing device 202 or to one or more target applications 210 running on client computing device 202. During a backup or other secondary copy operation, the client computing device 202 mounts the designated NFS path and writes data to that NFS path. The NFS path may be obtained from NFS path data 215 stored locally at the client computing device 202, and which may be a copy of or otherwise derived from NFS path data 219 stored in the secondary storage subsystem 218.

Write requests issued by client computing device(s) 202 are received by data agent 242 in secondary storage subsystem 218, which translates the requests and works in conjunction with media agent 244 to process and write data to a secondary storage device(s) 208, thereby creating a backup or other secondary copy. Storage manager 240 can include a pseudo-client manager 217, which coordinates the process by, among other things, communicating information relating to client computing device 202 and application 210 (e.g., application type, client computing device identifier, etc.) to data agent 242, obtaining appropriate NFS path data from the data agent 242 (e.g., NFS path information), and delivering such data to client computing device 202.

Conversely, during a restore or recovery operation client computing device 202 reads from the designated NFS network path, and the read request is translated by data agent 242. The data agent 242 then works with media agent 244 to retrieve, re-process (e.g., re-hydrate, decompress, decrypt), and forward the requested data to client computing device 202 using NFS.

By moving specialized software associated with system 200 such as data agent 242 off the client computing devices 202, the illustrative architecture effectively decouples the client computing devices 202 from the installed components of system 200, improving both scalability and plug-ability of system 200. Indeed, the secondary storage subsystem 218 in such environments can be treated simply as a read/write NFS target for primary storage subsystem 217, without the need for information management software to be installed on client computing devices 202. As one example, an enterprise implementing a cloud production computing environment can add VM client computing devices 202 without installing and configuring specialized information management software on these VMs. Rather, backups and restores are achieved transparently, where the new VMs simply write to and read from the designated NFS path. An example of integrating with the cloud using file system protocols or so-called “infinite backup” using NFS share is found in U.S. Patent Application No. 62/294,920, entitled “Data Protection Operations Based on Network Path Information.” Examples of improved data restoration scenarios based on network-path information, including using stored backups effectively as primary data sources, may be found in U.S. Patent Application No. 62/297,057, entitled “Data Restoration Operations Based on Network Path Information.”

Highly Scalable Managed Data Pool Architecture

Enterprises are seeing explosive data growth in recent years, often from various applications running in geographically distributed locations. FIG. 2C shows a block diagram of an example of a highly scalable, managed data pool architecture useful in accommodating such data growth. The illustrated system 200, which may be referred to as a “web-scale” architecture according to certain embodiments, can be readily incorporated into both open compute/storage and common-cloud architectures.

The illustrated system 200 includes a grid 245 of media agents 244 logically organized into a control tier 231 and a secondary or storage tier 233. Media agents assigned to the storage tier 233 can be configured to manage a secondary storage pool 208 as a deduplication store, and be configured to receive client write and read requests from the primary storage subsystem 217, and direct those requests to the secondary tier 233 for servicing. For instance, media agents CMA1-CMA3 in the control tier 231 maintain and consult one or more deduplication databases 247, which can include deduplication information (e.g., data block hashes, data block links, file containers for deduplicated files, etc.) sufficient to read deduplicated files from secondary storage pool 208 and write deduplicated files to secondary storage pool 208. For instance, system 200 can incorporate any of the deduplication systems and methods shown and described in U.S. Pat. No. 9,020,900, entitled “Distributed Deduplicated Storage System,” and U.S. Pat. Pub. No. 2014/0201170, entitled “High Availability Distributed Deduplicated Storage System.”

Media agents SMA1-SMA6 assigned to the secondary tier 233 receive write and read requests from media agents CMA1-CMA3 in control tier 231, and access secondary storage pool 208 to service those requests. Media agents CMA1-CMA3 in control tier 231 can also communicate with secondary storage pool 208, and may execute read and write requests themselves (e.g., in response to requests from other control media agents CMA1-CMA3) in addition to issuing requests to media agents in secondary tier 233. Moreover, while shown as separate from the secondary storage pool 208, deduplication database(s) 247 can in some cases reside in storage devices in secondary storage pool 208.

As shown, each of the media agents 244 (e.g., CMA1-CMA3, SMA1-SMA6, etc.) in grid 245 can be allocated a corresponding dedicated partition 251A-2511, respectively, in secondary storage pool 208. Each partition 251 can include a first portion 253 containing data associated with (e.g., stored by) media agent 244 corresponding to the respective partition 251. System 200 can also implement a desired level of replication, thereby providing redundancy in the event of a failure of a media agent 244 in grid 245. Along these lines, each partition 251 can further include a second portion 255 storing one or more replication copies of the data associated with one or more other media agents 244 in the grid.

System 200 can also be configured to allow for seamless addition of media agents 244 to grid 245 via automatic configuration. As one illustrative example, a storage manager (not shown) or other appropriate component may determine that it is appropriate to add an additional node to control tier 231, and perform some or all of the following: (i) assess the capabilities of a newly added or otherwise available computing device as satisfying a minimum criteria to be configured as or hosting a media agent in control tier 231; (ii) confirm that a sufficient amount of the appropriate type of storage exists to support an additional node in control tier 231 (e.g., enough disk drive capacity exists in storage pool 208 to support an additional deduplication database 247); (iii) install appropriate media agent software on the computing device and configure the computing device according to a pre-determined template; (iv) establish a partition 251 in the storage pool 208 dedicated to the newly established media agent 244; and (v) build any appropriate data structures (e.g., an instance of deduplication database 247). An example of highly scalable managed data pool architecture or so-called web-scale architecture for storage and data management is found in U.S. Patent Application No. 62/273,286 entitled “Redundant and Robust Distributed Deduplication Data Storage System.”

The embodiments and components thereof disclosed in FIGS. 2A, 2B, and 2C, as well as those in FIGS. 1A-1H, may be implemented in any combination and permutation to satisfy data storage management and information management needs at one or more locations and/or data centers.

Mobile Storage Manager Control Application

An information management system may include one or more client computing devices managed by a storage manager, a secondary storage computing device in communication with one or more secondary storage devices, a mobile computing device configured with a storage manager control application, and one or more networks through which the various devices and components of the information management system communicate. The storage manager control application may be configured to display information about the information management system on the mobile computing device, and allow a user of the mobile computing device to interact with the storage manager. In addition, the storage manager control application may allow the user to instruct the storage manager to perform various operations on the information management system, the secondary storage computing device, and/or one or more of the client computing devices. The storage manager control application may be specifically configured to operate on the mobile computing device, and to display information about the information management system using the limited resources available to the mobile computing device.

FIG. 3 illustrates an information management system 302 that can be managed via a storage manager control application 306 operating on a mobile computing device 304, in accordance with an example embodiment. The information management system 302 may include one or more client computing devices 308-310 in communication with various devices of the information management system 302 via one or more network(s) 312. In one embodiment, this devices include the storage manager 140, the secondary storage computing device 106, and the mobile computing device 304. The mobile computing device 304 may be a portable communications device used to communicate with the storage manager 140, such as a smartphone, a tablet computer, a wearable computing device (e.g., a smart watch), a handheld gaming device, or any other type of mobile computing device now known or later developed. As discussed below with reference to FIG. 2 , the storage manager control application 306 may implement one or more modules that allow the user of the mobile computing device 304 to control the storage manager 140 and to obtain information about the devices managed by the storage manager 140.

As shown in FIG. 3 , the storage manager 140 may manage one or more client computing device 308-310. The client computing devices 308-310 may be logically organized into one or more groups, and the storage manager 140 may be configured to coordinate and/or schedule backups of primary data for the one or more client computing devices 308-310. The secondary storage computing device 106 may create secondary copies of primary data for the one or more client computing device 308-310, and store the secondary copies in the secondary storage device 108. A description of backup operations and secondary copy operations provided by the secondary storage computing device 106 is discussed with reference to FIGS. 1A-2C.

The storage manager control application 306 is configured to manage the operations of the storage manager 140, and to obtain information about the backup protection for one or more of the client computing devices 308-310. To obtain this information and control the storage manager 140, the storage manager control application 306 may implement a variety of modules. FIG. 4 is a block diagram of the mobile computing device 304 from FIG. 3 , where the mobile computing device 304 instantiates the storage manager control application 306 having various different modules 412-424 for interacting with the storage manager 140 of FIG. 3 , in accordance with an example embodiment.

The mobile computing device 304 may execute and/or instantiate the storage manager control application 306. As briefly mentioned above, the mobile computing device 304 may be implemented as a smartphone, a tablet computer, a wearable computing device (e.g., a smart watch), a handheld gaming device, or any other type of mobile computing device now known or later developed. The form factor and computing resources of the mobile computing device 304 distinguishes such device from other desktop or laptop-based devices. For example, the mobile computing device 304 may have a more limited display area and less computing resources (e.g., processor speed, available cycles, available Random Access Memory, etc.) than a desktop or laptop-based computing device.

The mobile computing device 304 may include one or more hardware components found in a mobile computing device. In one embodiment, the mobile computing device 304 includes one or more processor(s) 402, one or more communication interface(s) 404 for communicating with the devices and/or components of the information management system 302, and one or more computer-readable medium(s) 406. The one or more computer-readable medium(s) 406 may store one or more application(s) 408 and data 410 that supports the functionalities provided by the one or more application(s) 408. The mobile computing device 304 may also include components typically found in a mobile computing device (e.g., a display, one or more input devices, a Global Positioning System transceiver, audio input/output devices, etc.), and a discussion of these components have been omitted for brevity and readability.

The application(s) 408 include various application(s) and/or module(s) that facilitate interactions with, and/or configuration of, the storage manager 140. In particular, the application(s) 408 may include a storage manager control application 306 executable within an operating system of the mobile computing device 304. Because of its complexity and breadth in functionalities, the storage manager control application 306 may include multiple modules 412-424 that handle various aspects of the storage manager 140 and/or interactions with such device. \Briefly mentioned here, and without limitation, the modules 412-424 may include a login module 412, a system status module 414, a client status module 416, a jobs module 418, a search module 420, a plan module 422, and an account module 424. Each of these modules may also store corresponding data 426-438 that support the functionalities that the modules 412-424 provide.

In one embodiment, the login module 412 provides access to the storage manager 140 and allows the user of the storage manager control application 306 to manage and control the storage manager 140. The login module 412 may generate a graphical user interface or other display that is initially displayed to the user when the user executes the storage manager control application 306. As the login module 412 may initially establish communications with the storage manager 140, the login module 412 may accept login information from the user of the storage manager control application 306, and store the login information as login data 426. The login information may include one or more types of information used to access the storage manager 140 and authenticate the user, which may include, but is not limited to, a username, a password, biometric information, a domain or group to which the user belongs, a storage manager name or server name for which the user desires access to, and other such information or combinations thereof. The login data 426 may be communicated to the storage manager 140 to authenticate the user of the storage manager control application 306, and grant the user access to administration of the storage manager 140.

FIG. 5 illustrates a graphical user interface 502 generated by the login module 412 for accessing the information management system 302 via the storage manager control application 306, in accordance with an example embodiment. In one embodiment, the graphical user interface 502 includes one or more input fields that allow the user to provide login information for accessing the storage manager 140. Initially, the one or more input fields may include a username input field and a server input field. The username input field may be an input field where the user may enter a series of alphanumeric characters corresponding tohis or her username for accessing the storage manager 140. The server input field may be an input field where the user may enter a series of alphanumeric characters corresponding to the server (or storage manager 140) that the user desires to access. After providing this information, the graphical user interface 502 may display a prompt (not shown) requesting that the user provide security credentials for authenticating himself or herself to the storage manager 140. The security credentials may include, but are not limited to, a password, a Personal Identification Number, biometric information (e.g., a fingerprint, facial scan, voice print, etc.), and other such security credentials or combinations thereof. Further still, the login module 412 may implement a 2-factor authentication, where the storage manager 140 (or another device within the information management system 302) contacts the user using a communication channel different than the communication channel used to initially log into the information management system 302. For example, the different communication channel may be a phone call, an e-mail to the user, a text message to the user, where the message of the different communication channel provides the user with a security token (e.g., a series of alphanumeric characters), and the user may be required to communicate the security token via the graphical user interface 502 to confirm his or her identity.

In addition, the login module 412 may encrypt or otherwise protect communications between the storage manager control application 306 and the storage manager 140. For example, the login module 412 may communicate with the storage manager 14 0 using the Transport Layer Security (“TLS”) protocol (e.g., Hypertext Transfer Protocol over TLS). Further still, where login information is stored in the mobile computing device 304 as login data 426, the login module 412 may encrypt the login data 426 so as to protect the login data 426 from unauthorized access by other programs and/or devices.

The login module 412 may permit a predetermined number of attempts for the user to authenticate himself or herself to the storage manager 140 via the login module 412. Where the user is unsuccessful in authenticating himself or herself, the login module 412 may display an error message indicating that his or her attempt was unsuccessful, and that the user has a limited number of attempts remaining. Once the user has used all of the remaining attempts, the login module 412 may prevent access to the storage manager 140 using the user's login credentials for a predetermined time period (e.g., five minutes, ten minutes, 30 minutes, etc.). Alternatively, where the user is successful in authenticating himself or herself to the storage manager 140, the login module 412 may instantiate the system status module 414, where the system status module 414 is configured to provide system status information for the information management system 302 managed by the storage manager 140.

FIGS. 6A-6B illustrate a continuous graphical user interface 602 generated by the system status module 414 of the storage manager control application 306, where the system status module 414 provides system status information about the information management system 302 of FIG. 3 , in accordance with an example embodiment. The graphical user interface 602 may include multiple display areas, discussed below, where each display area is dedicated to displaying particular system status information about the information management system 302.

In one embodiment, the mobile computing device 304 may have a limited display area for displaying all of the system status information at the same time. Accordingly, the graphical user interface 602 may be movable, or scrollable, based on a size of the display for the mobile computing device 304. The system status module 414 may generate and/or modify the graphical user interface 602 to be horizontally and/or vertically scrollable, depending on the size of the display for the mobile computing device 304. In this way, the graphical user interface 602 may be larger than the available display area of the mobile computing device 304, as shown in FIGS. 6A-6B.

In generating the system status information for the graphical user interface 602, the system status module 414 may communicate with the storage manager 140. In one embodiment, the system status module 414 communicates the username of the user that he or she used to access the storage manager control application 306 to the storage manager 140. In addition, the system status module 414 may submit a query for system status information that is associated with the username. To obtain the system status information in reply to the query, the storage manager 140 may reference the database 146, including one or more policies 148 and/or the index 150, to determine that system status information associated with the communicated username. In one embodiment, the user is associated with a security clearance, and the storage manager 140 references one or more policies of the policies database 148 that indicate the type of information a person having a particular security clearance is authorized to receive. For example, one or more of the policies 148 may associate particular security clearances with particular types of system status information. As a more particular example, a user having an “administrator” security clearance may be authorized to receive system status information relating to the number of client computing devices that are protected, the amount of available storage space in various secondary storage devices, the number of backup jobs that were successful, a number of backup jobs that were unsuccessful, and so forth. Accordingly, in one embodiment, the storage manager 140 determines which system status information to provide to the system status module 414 based upon the username of the user and the security clearance that he or she is associated with.

In replying to the system status module 414, the system status module 414 may store the received system status information as system status data 428. In addition, given the sensitivity of the system status information, the system status module 414 may encrypt or otherwise protect the system status data 428 while it is at rest within the mobile computing device 304.

After receiving the system status information (or portions of the system status information), the system status module 414 may display the received system status information via the graphical user interface 602. Referring first to FIG. 6A, this figure illustrates a first portion of the graphical user interface 602. The first portion of the graphical user interface 602 may display an overview section 604, where the overview section 604 provides general information about the protection (or backup) status of the client computing devices 308-310 of the information management system 302. As shown in FIG. 6A, the overview section 604 may display a percentage or other value (e.g., a number of actual client computing devices) of client computing devices that are “protected” within the information management system 302. In this context, the term “protected” generally means that a most recent backup job for a particular client computing device completed successfully. The client computing device is “protected,” in this context, because, should the client computing device experience a failure (e.g., malware, ransomware, a computer virus, etc.), the user of the affected client computing device will be able to restore his or her data from the most recent backup. In contrast, the term “unprotected” may mean or signify that a most recent backup job for a corresponding client computing device was not successful.

The terms “protected” and/or “unprotected” may take on other meanings depending on the configuration of the storage manager 140. For example, the term “protected” may mean that a client computing device is associated with a backup job and the term “unprotected” may mean that a client computing device is not associated with a backup job. As another example, the term “protected’ may mean that at least one backup job has completed successfully for a corresponding client computing device, and the term “unprotected” may mean that a client computing device has never been backed up. Accordingly, depending on the configuration of the storage manager 140, the terms “protected” and “unprotected” may have different meanings, and the user of the storage manager control application 306 will understand the meanings applicable to these terms given his or her authorization to access the information management system 302.

In addition to the overview section 604, the graphical user interface 602 may display secondary storage sections 606A-606E, where each secondary storage section 606A-606E is associated with a corresponding secondary storage computing device (e.g., secondary storage computing device 106) and/or a corresponding secondary storage device (e.g., secondary storage device 108). In the embodiment shown in FIG. 6A, the secondary storage sections 606A-606E show the secondary storage status for at least six secondary storage computing devices and/or secondary storage devices.

In addition to the secondary storage sections 606A-606E, the graphical user interface 602 may display selectable elements 612-616, where the selectable elements 612-616 cause different modules of the storage manager control application 306 to instantiate and/or activate, and to display a graphical user interface corresponding to the selected element. In one embodiment, the graphical user interface 602 display three selectable elements 612-616 for navigating through the various graphical user interfaces of the storage manager control application 306. These three selectable elements 612-616 may include a first selectable element 612 corresponding to a “home” or “starting” graphical user interface (e.g., the graphical user interface 602 shown in FIGS. 6A-6B), a second selectable element 614 corresponding to a “jobs” graphical user interface (e.g., the graphical user interface 802 shown in FIGS. 8A-8D), and a third selectable element 616 corresponding to a “user account” graphical user interface (e.g., the graphical user interface 1102 shown in FIG. 11 ). When the second selectable element 614 is selected, the selection may cause the storage manager control application 306 to instantiate and/or execute the jobs module 418. Similarly, when the third selectable element 616 is selected, the selection may cause the storage manager control application 306 to instantiate and/or execute the account module 424. The jobs module 418 and the account module 424 are each discussed with regard to FIGS. 8A-8D and FIG. 11 , respectively.

Returning to the secondary storage sections 606A-606E, the secondary storage status information may include different types of information for a corresponding secondary storage computing device and/or secondary storage device. In one embodiment, the secondary storage status information may include the name of the secondary storage device (e.g., a “disk library name”), an amount of space used within the secondary storage device (e.g., “used space”), an amount of total space available within the secondary storage device (e.g., “total space”), and an anticipated date when the secondary storage device is expected to be full and/or completely used (e.g., a “full date”). A secondary storage section may also display a graphic indicating an amount of space used and/or available within the secondary storage device, where the graphic uses a first color (e.g., red) to indicate an amount of storage space used in the secondary storage device and a second color (e.g., black) to indicate an amount of storage space available within the secondary storage device.

Although the embodiments of the secondary storage sections 606A-606E shown in FIG. 6A are associated with physical devices, the secondary storage sections 606A-606E may be associated with logical arrangements of storage. For example, one or more of the secondary storage sections 606A-606E may be associated with a storage volume of a secondary storage device rather than the secondary storage device itself. Accordingly, in this embodiment, a secondary storage section may display status and space information for the corresponding storage volume. Further still, the graphical user interface 602 may display a mixture of storage types in the secondary storage sections 606A-606E, where some secondary storage sections display secondary storage status information for a physical device and some secondary storage sections display secondary storage status information for logical volumes.

As explained above, the system status module 414 may obtain the system status information displayed in the graphical user interface 602 from the storage manager 140. To obtain the system status information, the storage manager 140 may query one or more indices and/or databases within the information management system 302, such as the media agent database 152 and/or the media agent index 153. The storage manager 140 may further query the management database 146 and/or the management index 150 to obtain this information. Where there are multiple secondary storage computing devices, the storage manager 140 may query each of the secondary storage computing devices to obtain the system status information requested by the system status module 414. In this manner, depending on the number of secondary storage computing devices within the information management system 302, the storage manager 140 may query multiple databases and/or secondary storage computing devices. Of course, in some instances, the storage manager 140 may store the system status information in the management database 146, in which case, the storage manager 140 may not query the secondary storage computing devices.

Referring next to FIG. 6B, is a continuation of the graphical user interface 602 displayed in FIG. 6A. FIG. 6B illustrates a second portion of the graphical user interface 602, where this second portion includes an unprotected client graph 608 and a selectable element 610. In one embodiment, the unprotected client graph 608 displays a number of client computing devices that are unprotected. In particular, the unprotected client graph 608 may comprise a number of sub-sections, where each sub-section corresponds to a reason why a client computing device is not protected. As shown in FIG. 6A, the unprotected client graph 608 may include five sub-sections, where a first sub-section corresponds to a set of client computing devices that are not associated with corresponding backup jobs, a second sub-section corresponds to a set of client computing devices that are filtered virtual machines, a third sub-section corresponds to a set of client computing devices that do not have a backup job scheduled, a fourth sub-section corresponds to a set of client computing devices that are associated with corresponding backup jobs that have failed, and a fifth sub-section corresponds to a set of client computing devices that are associated with backup jobs that are snapshot operations and do not have a corresponding backup copy. Additional and/or alternative types of sub-sections are also possible and are contemplated as falling within the scope of this disclosure.

A user may use the selectable element 610 to view those client computing devices that are not protected (e.g., the client computing devices that correspond to those shown in the unprotected client graph 608). By selecting the selectable element 610, the user may invoke the client status module 416, which then generates a separate graphical user interface for displaying client status information for one or more unprotected client computing devices of the information management system 302. FIG. 7 illustrates a graphical user interface 702 generated by the client status module 416 of the storage manager control application 306, where the client status module 416 provides client status information for one or more unprotected clients of the information management system 302, in accordance with an example embodiment.

With reference to FIG. 3 , in one embodiment, the client status module 416 is configured to communicate with the storage manager 140 to obtain client status information for one or more of the client computing devices 308-310 managed by the storage manager 140. The storage manager 140 may maintain client status information for one or more of the client computing devices 308-310 in the management database 146, such as by storing such client status information in the management index 150. Additionally, and/or alternatively, the secondary storage computing device 106 (or one or more other secondary storage computing devices) may maintain client status information for client computing devices 308-310 that are associated with the secondary storage computing device 106. In this context, the secondary storage computing device 106 may maintain client status information for a client computing device where the secondary storage computing device is configured to create secondary copies of primary data of the client computing device. The storage manager 140 may communicate with the secondary storage computing device 106 via one or more network(s) 312 and request client status information for the client computing devices associated with the secondary storage computing device. Although not specifically shown in FIG. 3 , the storage manager 140 may communicate with other secondary storage computing devices in a similar fashion where the information management system 302 includes multiple secondary storage computing devices configured to store and/or maintain secondary copies of primary data for one or more client computing devices 308-310.

With further reference to FIG. 4 , in response to the client status module 416, the storage manager 140 may communicate the client status information, where the client status module 416 stores the client status information as client status data 432. As with other types of data 410 stored by the storage manager control application 306, the client status module 416 may encrypt, or otherwise protect, the client status data 432 and display it when requested by the user of the storage manager control application 306.

In one embodiment, the client status information includes a variety of information for each of the client computing devices. In one embodiment, the client status information includes a client name for the client computing device, a most recent date and/or time when a backup job for the client computing device completed successfully, a most recent date and/or time when a backup job for the client computing device was scheduled, whether a most recent backup job has failed for the client computing device, and any reasons for the failure of the backup job (when applicable). The client status information may include additional and/or alternative types of client status information, and such client status information is contemplated as falling within the scope of this disclosure.

Referring briefly back to FIG. 6B, when a user selects the selectable element 610, the client status module 416 obtains client status information of those client computing devices that have failed backup jobs from the storage manager 140. Referring now to FIG. 7 , the client status module 416 may display the received client status information in the graphical user interface 702. In one embodiment, the client status module 416 is configured to display a plurality of client sections 704A-704E within the graphical user interface 702, where each client section 704A-704E corresponds to client a computing device. Using client section 704A as one example, the graphical user interface 702 displays that the client name is “aathithanmbp,” that the client computing device was last protected (e.g., backed up) on Dec. 18, 2020 at 10:42:42 A.M., and that the most recent backup job has failed (e.g., “Failure Reason: Backup job failed”). Other client sections 704B-704E show similar information. However, some of the client computing devices may not be “protected” because of a backup job failure, but for some other reason. For example, client sections 704C-704D show that corresponding client computing devices (e.g., “alocke840g3” and “amanning840”) are not protected because there is no corresponding backup job scheduled for these client computing devices.

While the graphical user interface 702 shows client status information for unprotected client computing devices, the graphical user interface 702 may also allow the user of the storage manager control application 306 to resolve outstanding issues and/or failures. In one embodiment, each of the client sections 704A-704E may include a selectable element 706A-706E, where the selectable element 706A-706E causes and/or instructs the storage manager 140 to execute one or more diagnostics on the corresponding client computing device. In one embodiment, the client status module 416 is configured with a set of instructions representing the diagnostics that are to be performed on a client computing device. Accordingly, when a user selects the selectable element (e.g., selectable element 706A), the client status module 416 may communicate these instructions to the storage manager 140 to perform on the corresponding client computing device. The instructions may include such operations as checking whether a backup job is configured for the corresponding client computing device, whether the corresponding client computing device is available and/or in communication with the storage manager 140, executing a temporary backup job on the client computing device to determine whether the client computing device can access its associated secondary storage computing device, and other such diagnostic operations. The storage manager 140 may then communicate the results of these instructions back to the client status module 416, which may then display the results of running the diagnostics on the corresponding client computing device.

In another embodiment, the storage manager 140 is configured with a set of instructions representing the diagnostics to perform on a corresponding client computing device and, when a user selects the selectable element 706A, the client status module 416 communicates an instruction to the storage manager 140 to perform diagnostics on the corresponding client computing device. In this embodiment, the instructions to perform the diagnostic operations may reside in a database associated with the storage manager 140 (e.g., the management database 146). When the storage manager 140 receives the instruction to perform the diagnostics on the corresponding client computing device, the storage manager 140 may perform the corresponding diagnostic operations on the client computing device, and then communicate the results to the client status module 416, which may store the results of the diagnostic operations as part of the client status data 432. The client status module 416 may then display the results of the diagnostic operations via the graphical user interface 702. In this way, the client status module 416 allows a user of the storage manager control application 306 to inspect and review the status of client computing devices at a granular level. This allows the user to make informed decisions about how to address particular problems that may have arisen with one or more of the client computing devices, and to develop solutions on a per-client basis. Such features allow the user to resolve issues with managed client computing device much more efficiently even if the user is remotely accessing the information management system 302.

Referring briefly back to FIG. 3 , the user may also interact with the graphical user interface 602 to view and/or interact with one or more backup jobs of the information management system 302. As explained previously, the user may select the second selectable element 614, which causes the storage manager control application 306 to engage and/or instantiate the jobs module 418, and cause a display of the graphical user interface 802 illustrated in FIGS. 8A-8D.

FIGS. 8A-8D illustrate the graphical user interface 802 generated by the jobs module 418 of a storage manager control application 306, where the jobs module 418 provides access to one or more backup jobs of the information management system 302, in accordance with an example embodiment. Referring initially to FIG. 8A, the graphical user interface 802 may include a number of job status sections 804A-804F, where each job section 804A-804F corresponds to a backup job managed by the storage manager 140.

In one embodiment, when the jobs module 418 is instantiated and/or executed, the jobs module communicates with the storage manager 140 to obtain job status information for one or more jobs managed by the storage manager 140. For example, the jobs module 418 may communicate a query to the storage manager 140 for the job status information for the client computing devices 308-310 of the information management system 302. To obtain the job status information, the storage manager 140 may reference one or more databases, such as the management database 146, and/or one or more indices, such as the management index 150. Additionally, and/or alternatively, the storage manager 140 may communicate one or more queries for job status information to one or more secondary storage computing devices within the information management system 302 (e.g., the secondary storage computing device 106).

In communicating the query for job status information, the jobs module 418 may generate a query that requests job status information for all backup jobs in the information management system 302. Alternatively, the jobs module 418 may generate a query that requests job status information for a particular type, or select group, of backup jobs within the information management system 302. For example, the jobs module 418 may generate a query for job status information for backup jobs that have failed or did not complete successfully. Thus, the job status information returned (e.g., communicated back) by the storage manager 140 to the jobs module 418 may depend on which types of backup jobs that the jobs module 418 identified in the query for job status information.

Referring briefly to FIG. 4 , when the storage manager 140 returns the requested jobs status information, the jobs module 418 may store the job status information as jobs data 434. As with other types of data 410 stored in the mobile computing device 304, the jobs module 418 may encrypt, or otherwise protect, the jobs data 434 to prevent unauthorized access by application(s) or third-party software other than the storage manager control application 306.

Referring back to FIG. 8A, the jobs module 418 generates the graphical user interface 802 that includes job status information for one or more backup jobs. In the embodiment shown in FIG. 8A, the jobs module 418 has displayed job status information for a variety of backup jobs. In displaying the graphical user interface 802, the jobs module 418 may generate one or more job status sections 804A-804F, where each job status section 804A-804F is associated with a corresponding backup job. In displaying the job status sections 804A-804F, the jobs module 418 may be configured to display job status sections 804A-804F based on one or more characteristics of the backup job. A characteristic of a backup job may include, but is not limited to, the client computing device type associated with the backup job (e.g., backup jobs for desktop computing devices, backup jobs for mobile computing devices, backup jobs for virtual machines, etc.), the frequency at which the backup job is executed (e.g., hourly, daily, weekly, etc.), the secondary storage device where secondary copies are stored for the backup job (e.g., a particular secondary storage device or name of a particular secondary storage device), whether the particular backup job was successful, and/or the execution status of the backup job (e.g., “running” (or currently being executed) or queued (waiting to be executed)), and other such backup job characteristics or combinations thereof.

The job status information for a backup job may include a variety of information. In one embodiment, the job status information may include a job identifier (e.g., a series of alphanumeric characters identifying the job), an execution status of the backup job, an amount of time that has elapsed since the backup job started executing, a type of backup job operation, a most recent time that the backup job was modified and/or updated, and a completion percentage indicating a percent that the backup job has completed or is remaining to be completed. As one example of these values, the job status section 804A shows that the job identifier is “22450617,” the execution status of the backup job is “Waiting” (e.g., has been paused), that the elapsed time of execution of the backup job is 236 minutes and 42 seconds, that the operation type is “Backup 3RD” (e.g., is a third backup of a client computing device), that the last update time of the backup job was performed on Dec. 5, 2020, and that the backup job is 81% completed. As explained above, the values of the job status information may be provided by the storage manager 140 and stored as jobs data 434 by the jobs module 418.

The jobs module 418 may be configured to allow a user to manipulate a particular backup job of one or more of the job status section 804A-804F. Referring to FIG. 8B is an example of the graphical user interface 802 where the jobs module 418 has displayed selectable elements 806-808 for interacting with a selected job status section 804A. In one embodiment, the jobs module 418 determines the selectable elements to display based on a selection of a job status section 804A. In particular, depending on whether the user of the storage manager control application 306 is authorized to view and/or manipulate a backup job associated with a corresponding job status section 804A, the jobs module 418 may display fewer and/or alternative selectable elements 806-808. In determining whether the user is authorized to view and/or manipulate a particular backup job, the jobs module 418 may communicate the username of the user to the storage manager 140, which, in turn, may determine those backup jobs for which the user is authorized to manipulate and/or view. For example, the storage manager 140 may reference the management database 146 to determine the authorization level of the user (e.g., “administrator,” “power user,” “user,” etc.), and then communicate a value indicating the user's authorization level to the jobs module 418. The jobs module 418 may be configured to grant access to manipulate one or more of the displayed job status sections 804A-804F based on the user's authorization level, where higher levels of authorization (e.g., “administrator” and/or “power user”) grant the user more access to backup jobs than lower levels of authorization (e.g., “user”). In this way, if the user is not authorized to view and/or manipulate a particular backup job, the jobs module 418 may not display one or more of the selectable elements 806-808.

In one embodiment, the selectable elements 806-808 include a first selectable element 806 associated with sending log file data to the storage manager control application 306. The first selectable element 806 allows the user to select log files related to one or more jobs and send the selected one or more jobs to a user via an upload. Log file data for a particular backup job may include a history of transactions for that backup job (e.g., one or more backup completion date(s), one or more failure date(s) for backups that failed, duration of a particular backup, the size of a backup, a number of files that were backed up, file names of files that were backed up, etc.). In this regard, log file data may form a complete record of backups for a particular backup job, whereas a jobs status section of the graphical user interface 802 may display

In this embodiment, the user of the storage manager control application 306 may select one or more of the job status sections 804A-804F, and then select the first selectable element 806. When the user selects the first selectable element 806, the jobs module 418 communicates one or more instructions to the storage manager 140 to send log file data for the backup jobs associated with the selected job status sections 804A-804F to the storage manager control application 306. The one or more instructions may include one or more job identifiers to identify the backup jobs to the storage manager 140. Based on these one or more instructions, the storage manager 140 may reference the management database 146 using the one or more job identifiers and retrieve log file data corresponding to the backup jobs associated with the one or more job identifiers. The storage manager 140 may then communicate the log file data to the jobs module 418, which may then store the log file data as jobs data 434, and associate the log file data with corresponding job status sections 804A-804F. The user of the storage manager control application 306 may then view the received log file data for a corresponding backup job for selecting the job section associated with the corresponding backup job. In this way, the user of the storage manager control application 306 may view log file data with selected backup jobs (e.g., selected by way of selecting one or more job status sections 804A-804F), which can help the user better understand any anomalies in the backup process and/or the configuration of a particular backup job.

The selectable elements 806-808 may also include a second selectable element 808 corresponding to viewing additional details about a backup job associated with a selected job status sections 804A-804F. In one embodiment, the second selectable element 808 may be disabled until the user has requested log file data for a particular backup job (e.g., by selecting the first selectable element 806 after selecting a particular job status section 804A-804F). When the user selects the second selectable element 808 after selecting a particular job status section, the graphical user interface 802 may retrieve log file data for backup job corresponding job status section from the jobs data 434, and display the log file data via the display of the mobile computing device 304. In another embodiment, selecting the second selectable element 808 may cause the jobs module 418 to determine whether log file data is stored in the jobs data 434 for the corresponding backup job and, if so, display the log file data via the display of the mobile computing device 304. Should the jobs module 418 determine that log file data does not exist for the corresponding backup job, the jobs module 418 may communicate an instruction to the storage manager 140 to send the log file data for the corresponding backup job (e.g., based on the job identifier of the corresponding backup job). When the jobs module 418 receives the requested log file data, the jobs module 418 may then display the log file data as the additional details corresponding to the second selectable element 808.

Referring next to FIG. 8C, is an illustration of the graphical user interface 802, where additional selectable elements 810-814 have been displayed. The selectable elements 810-814 include a first selectable element 810 corresponding to a suspension of all backup jobs, a second selectable element 812 corresponding to a resumption of one or more suspended backup jobs, and a third selectable element 814 corresponding to a termination of one or more backup jobs (e.g., a backup job in progress or a backup job waiting to be executed). In one embodiment, selecting a selectable element 810-814 causes the jobs module 418 to send an instruction to the storage manager 140 with an instruction to perform the operation associated with the selected selectable element. For example, selecting the first selectable element 810 causes the jobs module 418 to send an instruction to the storage manager 140 to suspend all backup jobs in progress and/or all scheduled backup jobs. The selectable elements 810-814 allow a user of the storage manager control application 306 to control the operation of backup activities within the information management system 302 without having to be physically present at a desktop computing device ordinally used to manage the storage manager 140. This allows the user to be more mobile than other implementations and can allow the user to visit other physical devices (e.g., other computing devices managed by the storage manager 140) while controlling the backup activities of the information management system 302.

Recognizing that permitting access to the control of one or more backup jobs can be inherently risky, the storage manager 140 may perform an authorization check on the username of the user prior to executing the requested operation. In this regard, each of the operations corresponding to the selectable elements 810-814 may be associated with one or more authorization levels (e.g., “administrator,” “operator,” “power user,” etc.). Where the user of the storage manager control application 306 does not have the requisite authorization to perform a particular operation, the storage manager 140 may deny or may not perform the requested operation associated with the selected selectable element. As one example, suppose that a user of the storage manager control application 306 has a “power user” level of authorization. In this example, further suppose that the operation of killing all backup jobs is associated with the levels of authorization of “administrator” and “operator.” Accordingly, in this example, were the user to select the third selectable element 814, the storage manager 140 first determines the level of authority to perform the requested operation (e.g., by referencing the management database 146), then determines the level of authority of the user (e.g., by also referencing the management database 146 or another database), then compares the authority level of the user with the authority level of the requested operation, and finally, determines that the user does not have requisite authority. From this example, the storage manager 140 may communicate a message to the storage manager control application 306 that the user does not have the requisite authority to perform the requested operation. Alternatively, should the user have the requisite authority, the storage manager 140 may perform a similar set of retrievals and determinations, perform the requested operation, and then communicate a message to the storage manager control application 306 that the operation was performed (e.g., and/or performed successfully). In this manner, the storage manager 140 and/or the information management system 302 may implement a set of security controls to prevent unauthorized users from performing certain operations on the backup jobs, while allowing authorized users to perform such operations. This ensures that the storage manager control application 306 can be distributed to users with different types of authorization levels and scopes of control.

Referring next to FIG. 8D, is an embodiment of the graphical user interface 802 where the graphical user interface 802 displays a job filter overlay 816 that allows the user to view and/or selectable particular types of backup jobs from the available backup jobs in the information management system 302. In one embodiment, the job filter overlay 816 displays a first selectable option 818 corresponding to anomalous jobs and a second selectable option 820 corresponding to all backup jobs scheduled to perform and/or having been performed within a particular time period (e.g., one day, two days, three days, a week, etc.). In another embodiment, the job filter overlay 816 may include multiple selectable options, where each selectable option corresponds to the status of the backup job. When the user selects the first selectable option 818, the jobs module may send an instruction to the storage manager 140 to send job status information for one or more backup jobs that did not complete successfully on the prior backup attempt (e.g., are “anomalous” backup jobs). The storage manager 140 may reference the management database 146 to obtain job status information for one or more backup jobs that did not complete successfully on the most recent backup attempt, and communicate the obtained job status information to the jobs module 418. Additionally, and/or alternatively, the storage manager 140 may also communicate with one or more secondary storage computing devices (e.g., the secondary storage computing device 106), and instruct the one or more secondary storage computing devices to send job status information to the storage manager 140 for one or more backup jobs that did not complete successfully on the most recent backup attempt. The jobs module 418 may receive the job status information for the anomalous backup jobs from the storage manager 140, and store such job status information as jobs data 434. The jobs module 418 may then update the graphical user interface 802 with the job status information for the anomalous backup jobs (e.g., backup jobs corresponding to the first selectable option 818).

With regard to the second selectable option 820, this selectable option 820 may correspond to a request to view job status information for all backup jobs managed by the storage manager 140. In one embodiment, the second selectable option 820 corresponds to backup jobs that have been performed, or will be performed, within a predetermined time period. The second selectable option 820 may be associated with a predetermined time period so as to limit the amount of job status information displayed in the graphical user interface 802. This is helpful because the mobile computing device 304 may have a limited display, and displaying too much job status information may be challenging to the user of the mobile computing device 304 to review and/or access such job status information. As with the first selectable option 818, the jobs module 418 may communicate an instruction to the storage manager 140 to obtain job status information for one or more backup jobs that have been performed, or will be performed, within a predetermined time period (e.g., one day). The storage manager 140 may reference the management database 146 and/or communicate with one or more secondary storage computing devices to obtain such job status information, and then communicates the requested job status information to the jobs module 418. In turn, the jobs module 418 may store the requested job status information as jobs data 434, from which the jobs module 418 may retrieve it in displaying the graphical user interface 802. In this way, the job filter overlay 816 allows the user to selectively choose which types of backup jobs he or she desires to view and/or manipulate, and provides an additional tool to the user in managing the backup jobs of the information management system 302. Thus, the jobs module 418 provides a number of features to the user of the storage manager control application 306 for managing and interacting with backup jobs of one or more client computing devices 308-310.

In addition to interacting with various client computing devices 308-310 and one or more backup jobs, the storage manager control application 306 may also provide search functionalities allowing the user to find various entities and/or objects within the information management system 302. Accordingly, the storage manager control application 306 may implement a search module 420 that provides these functionalities. FIGS. 9A-9E illustrate a graphical user interface 902, generated by the search module 420, where the graphical user interface 902 provides various interactive elements that allow the user to search for such entities and/or objects, in accordance with an example embodiment.

In one embodiment, the graphical user interface 902 includes several elements and/or sections 904-908 that allow the user to search for various entities and/or objects within the information management system 302. In this context, an entity and/or object may be a logical entity/logical object or a physical entity/physical object. Examples of logical entities and/or logical objects include, but are not limited to, backup plans, backup jobs, client groups, media agents, data agents, virtual machines, storage volumes, and other such logical constructs, objects, and/or entities. Examples of physical entities and/or physical objects include, but are not limited to, client computing devices, secondary storage devices, primary storage devices, mobile computing devices, the storage manager 140, file servers, and any other type of physical device and/or object.

The graphical user interface 902 may include a search query input element 904, where the user may enter one or more alphanumeric characters representing a search query. The search query may be a partial word, a complete word, a partial phrase, a complete phrase, or any combinations of the foregoing. When the user enters the search query and presses a submission element (e.g., a “Return” or “Enter” key on a hard- or soft-keyboard), the search module 420 may communicate the search query to the storage manager 140. The storage manager 140 may then parse the search query using one or more query parsing techniques and/or search query parsing Application Programming Interfaces (e.g., the Apache® Lucene API) to parse the submitted search query, and then conducts a search on one or more databases (e.g., the management database 146) to find and/or match records of entities and/or objects, where the records of the entities and/or objects include entity names and/or object names that match the submitted search query. The storage manager 140 may also communicate one or more instructions to one or more secondary storage computing devices that instruct the one or more secondary storage computing devices to conduct their own searches using one or more of the aforementioned techniques, and to return the search results to the storage manager 140. The storage manager 140 may also search one or more of the network(s) 312 for records and/or names of entities and/or objects that match the submitted search query. The storage manager 140 may then compile a listing of search results that match the submitted search query, and then communicate the listing to the search module 420.

Each search result in the search result listing may include information about the search result. The information about the search result may include such characteristics as the name of the entity and/or object, the type of the entity and/or object, an Internet Protocol address of the entity and/or object, a device association and/or location of the entity and/or object (e.g., where the search result is a secondary storage device or primary storage device), and other such information or combinations thereof. The information that is included in a search result may be dependent on the type of entity in the search result. Thus, where one search result is a physical device, the search result may include an IP address for the device; where another search result is a logical entity and/or object, the search result may include a computing device with which the logical entity and/or object is associated. Accordingly, different types of search results may have different types of information included in the search result. Examples of search results are discussed with reference to FIG. 9B, below.

Turning next to other elements of the graphical user interface 902, the graphical user interface 902 may also include a quick search section 906, where a user may select one or more options for conducting a quick search of entities and/or objects within the information management system 302. The search module 420 may be programmed and/or previously configured to display a specific set of options in the quick search section 906. As shown in FIG. 9A, examples of preconfigured or programmed search options include, but are not limited to, “Clients,” “Client Groups,” “Plans,” and/or “Media Agents.” Other options may include, for example, “Virtual Machines,” “Data Agents,” “Media Agents,” “Secondary Storage Volumes,” and so forth.

As with the search query input element 904, a selection of one or more options from the quick search section 906 may cause the search module 420 to communicate an instruction to the storage manager 140 to perform a search for entities and/or objects within the information management system 302 that match the selected quick search option. For example, selecting the “Clients” quick search option may cause the search module 420 to communicate an instruction to the storage manager 140 to perform a search for entities and/or objects within the information management system 302 that are “Clients.” In performing the search using the quick search option, the storage manager 140 may search one or more databases, such as the management database 146, and may search one or more indices, such as the management index 150. The storage manager 140 may also communicate an instruction to one or more secondary storage computing devices 106 to perform similar searches within one or more databases, such as the media agent database 152 and/or the media agent index 153. The storage manager 140 may also search the one or more network(s) 312 using one or more searching techniques to identify client computing devices 308-310 (and/or client computing device groups) that match the selected quick search option. After conducting the search, the storage manager 140 may communicate one or more search results to the search module 420, where the search module 420 stores the search results as search data 436. The search module 420 may then display the search results in the graphical user interface 902, examples of which are discussed with reference to FIG. 9B.

The graphical user interface 902 may also display a recent search section 908, where the search module 420 displays recent searches conducted using the search query input element 904. In one embodiment, the search module 420 is configured to store a predetermined number of prior search queries (e.g., the most recent five search queries). A user may select a search query appearing the recent search section 908 to perform a search using the selected search query. Additionally, and/or alternatively, the user may instruct the search module 420 to delete a particular recent search query from the recent search section 908. The search module 420 may store the recent search queries as search data 436.

Referring next to FIG. 9B is the graphical user interface 902 displaying one or more search results 910A-910C communicated by the storage manager 140. In one embodiment, the search module 420 groups search results 910A-910C according to the entity type or object type of the search result. Thus, the search results 910A-910C may be grouped into such search result groups as “Hypervisors,” “Media Agents,” “File Servers,” “Clients,” “Client Groups,” “Virtual Machines,” and so forth. As shown in FIG. 9B, the search results 910A-910C were found based on the search query “marvel” and are grouped into three entity types or three object types, namely, “Hypervisors,” “Media Agents,” and “File Servers.” Using the search module 420 and the graphical user interface 902, the user of the storage manager control application 306 may then instruct the various entities and/or objects listed as search results 910A-910C to perform one or more operations, as discussed with reference to FIG. 9C and FIG. 9D.

Referring collectively to FIGS. 9C-9D, are examples of operations menus 912A-912B that may be displayed based on a selected search result from the displayed search results 910A-910C. In one embodiment, the operations menus 912A-912B include one or more selectable options, where each option is associated with an operation that an entity and/or object may perform. Furthermore, the options displayed in the first operations menu 912 may vary depending upon the entity and/or object selected from the displayed search results. For example, the selectable options shown in FIG. 9C are those selectable options associated with the operations that a media agent may perform when the user selects a media agent from the displayed search results. (e.g., the search result 910B from FIG. 9B).

In one embodiment, the search data 436 includes information about the operations to display for a given entity and/or object type. For example, the search data 436 may include an array, table, matrix, structured language file, or any other data structure, that associates operations to display in the operation menu with particular object types. Thus, the search data 436 may include associations between operations and entity and/or object types such as media agents, hypervisors, file servers, clients, client groups, users, plans, or any other entity and/or object type. Thus, when a user selects an entity and/or object from the displayed search results, the search module 420 references these associations to determine which operations to display in the operations menus 912A-912B.

As an additional element of security, not every displayed operation may be selectable and/or activatable by the user. As discussed above, the user of the storage manager control application 306 may be associated with a particular authorization (e.g., security) level, and one or more operations displayed in the operations menu 912A-912B may require a particular authorization (or a particular authorization level and higher levels of authorization) to activate. In this regard, the search module 420 may determine whether the user is authorized to select an operation displayed in the operations menu 912A-912B. The search module 420 may display the option for the operation so as to inform the user as to the options that are, in fact, available, but may disable activation of the operation where the user is not authorized to engage such operation. As explained before, the search module 420 may communicate with the storage manager 140 to determine the user's authorization level. Should the search module 420 have previously determined the user's authorization level, information about the user's authorization level may be stored in the search data 436, and the search module 420 may reference this stored information in determining whether the user is authorized to execute a particular operation for one or more of the displayed search results.

Referring briefly to FIG. 9D and FIG. 9E, the options displayed in the operation menu 9128 may be those operations associated with a file server, and the options 914-914B may be those operations associated with a user. When a user selects one or more of the options from the graphical user interface 902 shown in any of FIGS. 9C-9E, the search module 420 may communicate one or more instructions to the storage manager 140, where the one or more instructions include the selected operation and the desired entity that is to perform (or on which to perform) the selected operation. Accordingly, when the storage manager 140 receives the one or more instructions, the storage manager 140 may communicate an instruction to the appropriate entity to perform the selected operation. In some instances, an entity other than the one selected may perform the selected operation (e.g., a user object does not disable himself or herself; rather, a directory server or other computing device disables the user account associated with the user). Where the operation is successful, the storage manager 140 may communicate a message to the search module 420 informing the search module 420 that the operation was performed, and that the operation was performed successfully. Should the operation not be performed successfully, the storage manager 140 may communicate a message to the search module 420 informing the search module 420 of the failure. Where the message is a success message, the search module 420 may update the graphical user interface 902 with a prompt or other message informing the user that the operation was a success. Where the message from the storage manager 140 is a failure message, the search module 420 may update the graphical user interface 902 with a prompt or other message informing the user that the operation did not succeed or failed. Should the storage manager 140 include a brief reason for the failure (e.g., the computing device communicated a failure reason to the storage manager 140), the search module 420 may also display the failure reason.

In this way, the search module 420 allows the user of the storage manager control application 306 to search for various entities and/or objects throughout the information management system 302. This is particularly useful in instances where the user may have a notion of the entity and/or object he or she is looking for, but is not entirely certain as to the name of the entity and/or object. Furthermore, because the search module 420 allows the user to engage in operations on selected entities and/or objects, the user may use the storage manager control application 306 to effectively control various entities and/or objects throughout the information management system 302. This can be useful in instances where the user is in a location different than the location of the selected entity and/or object, and travel to the selected entity and/or object may not be timely and/or possible (e.g., the user is located in a city several hours away from the selected entity and/or object). Thus, the search module 420 provides a number of technological benefits to the storage manager control application 306 beyond simply displaying information, and facilitates interactions between the user of the storage manager control application 306 and entities and/or objects within the information management system 302.

In addition to engaging and/or interacting with physical entities and/or objects, within the information management system 302, the storage manager control application 306 may implement a plan module 422 that allows a user to manage one or more backup plans configured in the information management system 302. FIG. 10 illustrates a graphical user interface 1002 generated by the plan module 422, where the plan module 422 allows the user to review backup plans configured within the information management system 302. In one embodiment, the graphical user interface 1002 displays one or more backup plans, where each backup plan may be selected by the user for further review and/or inspection. When a backup plan is selected, the plan module 422 may display selectable options 1004A-1004B, where a first selectable option 1004A is associated with viewing volume and/or device associations for the selected backup plan, and the second selectable option 1004B is associated with viewing details about the selected backup plan.

In this regard, a backup plan may include associations between data source(s) and data destination(s), where a data from the data source is backed up to the data destination. A data source may include a client computing device, a primary storage device, a virtual machine, a logical disk volume, or any other type of data source. A data destination may include a secondary storage computing device, a secondary storage device, a disk volume of a secondary storage device, or any type of data destination.

In addition, one or more computing devices may be associated with a particular backup plan. For example, the backup plan may include scheduling information (e.g., frequency of backup), the data destination, the client computing devices from which primary data is obtained, a number of backup copies to create for a particular data source (e.g., a client computing device, disk volume, disk partition, etc.), and other such backup plan information. As one or more client computing devices may require similar backup schedules, data destinations, a same number of backup copies, and so forth, a backup plan may be configured to encompass multiple client computing devices.

Accordingly, when a backup plan from the graphical user interface 1002 and the first selectable option 1004A are selected, the plan module 422 may communicate an instruction to the storage manager 140 to provide a listing of the associations with the selected backup plan. As in other operations previously discussed, the storage manager 140 may reference one or more databases, such as the management database 146, to obtain the associations of the selected backup up. In one embodiment, the associations may include a listing of the client computing devices that are associated with the selected backup plan. In another embodiment, the associations may include a listing of the associations between data source(s) and data destination(s). A third embodiment may include a combination of the foregoing two embodiments. The storage manager 140 may then communicate the associations to the plan module 422, which may store the received associations as plan data 438. The plan module 422 may then display the received associations via the graphical user interface 1002 for review by the user.

The graphical user interface 1002 may also display a second selectable option 1004B that allows the user to view backup plan details for a selected backup plan. As shown in FIG. 10 , the backup plan information initially shown in the graphical user interface 1002 may be a portion of the total amount of information for a given backup plan. In one embodiment, the graphical user interface 1002 displays a summary for each of the displayed one or more backup plans. A summary may include, but is not limited to, the name of the backup plan, a projected and/or estimated recovery point objective for the backup plan, a number of backup copies that are created under the backup plan, and a number of entities that are associated with the backup plan. By selecting the selectable option 1004B, the plan module 422 may obtain more complete backup plan information for the selected backup plan. Similar to one or more of the operations previously discussed, the plan module 422 may communicate an instruction to the storage manager 140 to obtain backup plan information for the selected backup plan, where the storage manager 140 may reference one or more of the databases in the information management system 302 to obtain this information (e.g., the management database 146). The storage manager 140 may communicate the obtained backup plan information to the plan module 422, which may store the backup plan information as part of the plan data 438. The backup plan information that may be displayed from selecting the second selectable option 1004B may include, but is not limited to, the name of the backup plan, the schedule at which the backup plan occurs, the names and/or Internet Protocol addresses of entities associated with the backup plan, the most recent time the backup plan executed successfully, the amount of data backed up by the backup plan, the data destination(s) of the backup plan, the next time the backup plan is scheduled to execute, and any other such backup plan information or combinations thereof.

In this way, the plan module 422 allows the user of the storage manager control application 306 to review backup plans configured within the information management system 302, which can help the user better understand the backup objectives of the information management system 302. It can also help the user understand which entities are covered and/or not covered by a particular backup plan, and help the user pinpoint whether there have been any problems with prior executions of backup plans. Thus, the plan module 422 provides several important features that allow the user to understand the backup architecture of the information management system 302, and whether additional configurations are required.

Furthermore, the storage manager control application 306 may allow the user to review and/or interact with various options for the user account of the user using the storage manager control application 306. Briefly referring to FIG. 4 , and in one embodiment, the storage manager control application 306 includes an account module 424 that provides access to, and interactions with, the user account of the user. FIG. 11 illustrates a graphical user interface 1102 generated by the account module 424, where the account module 424 allows a user to interact with various account settings and configurations of a user account, in accordance with an example embodiment.

In one embodiment, the graphical user interface 1102 displays information about the storage manager control application 306. The information about the storage manager control application 306 may include the storage manager 140 that the storage manager control application 306 is interacting with (e.g., “drive.mettallic.io”), the user name of the user using the storage manager control application 306 (e.g., “Parminder Singh”), the current version of server software being executed by the storage manager 140 (e.g., “5.4”), and the current version of the storage manager control application 306 (e.g., “5.4”). This information may be stored as account data 430. The graphical user interface 1102 may display one or more selectable options 1104A-1104E, where each selectable option 1104A-1104E corresponds to a different feature and/or operation.

The selectable options 1104A-1104E may include a first selectable option 1104A that allows the user to provide feedback and/or commentary about the storage manager control application 306. When the first selectable option 1104A is selected, the account module 424 may display another graphical user interface or prompt (not shown), where the user can provide and/or input feedback and/or commentary. Once entered, the storage manager control application 306 may communicate the feedback and/or commentary to the storage manager 140, where the feedback and/or commentary is stored for later review by an authorized user of the information management system 302.

A second selectable option 11048 may allow the user to check for updates to the storage manager control application 306. When the user selects the second selectable option 1104 b, the storage manager control application 306 may communicate a query or instruction to the storage manager 140, where the query or instruction includes a request to check for updates and a current version of the storage manager control application 306. The storage manager 140 may compare the current version of the storage manager control application 306 with the most recent version of the storage manager control application 306. For example, the storage manager 140 may maintain a repository of versions of the storage manager control application, where each version is associated with an installable copy of the storage manager control application.

Where the storage manager 140 determines that the version of the storage manager control application 306 being used by the user is different (e.g., older) than the most recent version of the storage manager control application, the storage manager 140 may communicate a message to the account module 424 informing the account module 424 that an update to the storage manager control application 306 is available. The account module 424 may then display a prompt or message informing the user that an update to the storage manager control application 306 is available and an option to update the storage manager control application 306. Where the user selects the option to update the storage manager control application 306, the account module 424 may communicate a request for the updated version of the storage manager control application 306. The storage manager 140 may then send the updated version of the storage manager control application to the account module 424, which may then proceed with the installation of the update. In another embodiment, when the account module 424 is informed that an update is available, the account module 424 may automatically update the storage manager control application 306 using the available update.

The selectable options 1104A-1104E may also include a third selectable option 1104C that, when selected, instructs the account module 424 to send log data for the storage manager control application 306 to a designated server (e.g., the storage manager 140). The designated server may then store the log data in one or more databases (e.g., the management database 146) for later review and investigation by an administrator and/or operator of the information management system 302.

A fourth selectable option 1104D may, when selected, instruct the account module 424 to change the overall look and/or appearance of the storage manager control application 306. For example, selecting the fourth selectable option 1104D may change one or more colors shown in one or more of the aforementioned graphical user interfaces including, but not limited to, text colors, background colors, foreground colors, outline colors, and other such colors shown in one or more of the graphical user interfaces. In the embodiment shown in FIG. 11 , the fourth selectable option 1104D is labeled as “Switch to dark theme” because, when selected, the account module 424 changes one or more colors of the graphical user interfaces so that, instead of dark text showing up against a light background (e.g., a “light theme”), a light color text (e.g., white or grey) is presented against a dark or black screen. Although not specifically shown in FIG. 11 , when the storage manager control application 306 is displayed in the dark theme, the text of the fourth selectable option 1104D may display “Switch to light theme.” Whether the user has selected a light theme or a dark theme may be stored as part of the account data 430.

A fifth selectable option 1104E may, when selected, instruct the account module 424 to log the current user out of the account being used to interact with the storage manager control application 306. Logging out of the storage manager control application 306 may cause the account module 424 to instantiate the login module 412, which may then display the graphical user interface 502 previously discussed with reference to FIG. 5 . Logging out may also cause the account module 424 to delete one or more types of data 426-430 from the data 410 to prevent against unauthorized access.

In this way, this disclosure provides a storage manager control application that allows a user to remotely control and interact with a storage manager of an information management system. As the storage manager control application is designed for a mobile computing device, the storage manager control application is optimized to use the limited computing resources and limited display area of the mobile computing device. The storage manager control application may be implemented using a variety of modules, each of which contribute numerous features

Example Embodiments

Some example enumerated embodiments of the present invention are recited in this section in the form of methods, systems, and non-transitory computer-readable media, without limitation. In one embodiment, this disclosure describes a system for managing and configuring a storage manager of an information management system, wherein the system includes one or more non-transitory, computer-readable mediums having computer-executable instructions stored thereon, and one or more processors that, having executed the computer-executable instructions, configure the system to perform a plurality of operations. The plurality of operations may include displaying a first graphical user interface on a mobile computing device, wherein the first graphical user interface comprises a plurality of elements, including a search query input element configured to receive a search query and a quick search section. The quick search section displays at least one quick search option for conducting a search within the information management system, and the at least one quick search option corresponds to an entity type of an entity within the information management system. The first graphical user interface also include a recent search section, wherein the recent search section displays at least one previously submitted search query used to conduct a search within the information management system.

The plurality of operations may further include receiving a search query from at least one of an input into the search query input element, a selection of the at least one quick search option, or the at least one previously submitted search query, and transmitting a first instruction to a storage manager in communication with the mobile computing device to perform a search within the information management system using the received search query.

The plurality of operations may also include receiving at least one search result from the storage manager in response to the transmitted first instruction, displaying the at least one search result on the first graphical user interface, receiving a second instruction for the at least one search result to perform an operation, and communicating the second instruction to the storage manager, wherein the storage manager is configured to communicate the second instruction to the at least one search result to perform the operation.

In another embodiment of the system, the plurality of operations further comprises displaying a second graphical user interface, wherein the second graphical user interface comprises an overview section associated with the information management system, wherein the overview section displays a graphic indicating a protection status of client computing devices within the information management system, and at least one secondary storage section associated with a secondary storage device, wherein the at least one secondary storage section includes storage status information for the secondary storage device. The plurality of operations may also include receiving a third instruction using the second graphical user interface to display information about client computing devices that are not protected with a backup in the information management system, and communicating the third instruction to the storage manager to obtain the information about the client computing devices that are not protected with a backup.

The plurality of operations may further include receiving the information about the client computing devices that are not protected with a backup in response to the third instruction, and displaying the information about the client computing devices that are not protected with a backup in a third graphical user interface different from the second graphical user interface.

In a further embodiment of the system, the plurality of operations further comprises displaying a second graphical user interface that includes at least one client section corresponding to a client computing device, where the at least one client section is displayed based on the client computing device not being protected with a corresponding backup, and receiving a third instruction using the second graphical user interface to perform a diagnostic on the client computing device to resolve an issue with the client computing device not being protected with the corresponding backup. The plurality of operations may also include communicating the third instruction to the storage manager to perform the diagnostic on the client computing device, receiving a result of the diagnostic performed on the client computing device from the storage manager based on the communicated third instruction, and displaying the result of the diagnostic on the second graphical user interface.

In yet another embodiment of the system, the plurality of operations further comprises displaying a second graphical user interface that includes at least one job status section, wherein the at least one job status section displays job status information for a corresponding backup job established in the information management system, and the job status information includes at least a job identification number, an execution status of the backup job, and an operation type indicating a backup job type of the backup job.

In yet a further embodiment of the system, the plurality of operations further comprises displaying a plurality of selectable elements for interacting with a plurality of job status sections displayed in the second graphical user interface, wherein at least one selectable element of the plurality of selectable elements corresponds to an instruction to suspend one or more backup jobs corresponding to the plurality of job status sections. The plurality of operations may also include receiving a selection of the at least one selectable element to suspend the one or more backup jobs, communicating a third instruction to the storage manager to suspend the one or more backup jobs based on the received selection, and receiving a message from the storage manager indicating whether the suspension of the one or more backup jobs was successful. The plurality of operations may further include displaying a prompt corresponding to the suspension of the one or more backup jobs on the second graphical user interface based on the received message.

In another embodiment of the system, the plurality of operations further comprises displaying a job filter overlay overlaid the second graphical user interface, wherein the job filter overlay includes a plurality of selectable options that allow the user to filter backup jobs from the second graphical user interface based on a status of the backup job, receiving a selection of a selectable option corresponding to a particular status, and updating the second graphical user interface to display only those job status sections from the plurality of job status sections that match the selected selectable option.

In a further embodiment of the system, a plurality of search results is received in response to the transmitted first instruction, each search result of the plurality of search results corresponds to a particular entity type, and each search result is displayed on the first graphical user interface in a search result group corresponding to the particular entity type of the search result such that search results of different entity types are not displayed into a same search result group.

This disclosure further describes a method for managing and configuring a storage manager of an information management system, wherein the method comprises displaying a first graphical user interface on a mobile computing device, wherein the first graphical user interface comprises a plurality of elements, including a search query input element configured to receive a search query, and a quick search section, wherein the quick search section displays at least one quick search option for conducting a search within the information management system, and the at least one quick search option corresponds to an entity type of an entity within the information management system. The first graphical user interface may also display a recent search section, wherein the recent search section displays at least one previously submitted search query used to conduct a search within the information management system. The method may further include receiving a search query from at least one of an input into the search query input element, a selection of the at least one quick search option, or the at least one previously submitted search query, and transmitting a first instruction to a storage manager in communication with the mobile computing device to perform a search within the information management system using the received search query.

The method may also include receiving at least one search result from the storage manager in response to the transmitted first instruction, displaying the at least one search result on the first graphical user interface, receiving a second instruction for the at least one search result to perform an operation, and communicating the second instruction to the storage manager, wherein the storage manager is configured to communicate the second instruction to the at least one search result to perform the operation.

In another embodiment of the method, the method includes displaying a second graphical user interface, wherein the second graphical user interface comprises an overview section associated with the information management system, wherein the overview section displays a graphic indicating a protection status of client computing devices within the information management system, and at least one secondary storage section associated with a secondary storage device, wherein the at least one secondary storage section includes storage status information for the secondary storage device. The method may further include receiving a third instruction using the second graphical user interface to display information about client computing devices that are not protected with a backup in the information management system, and communicating the third instruction to the storage manager to obtain the information about the client computing devices that are not protected with a backup. The method may also include receiving the information about the client computing devices that are not protected with a backup in response to the third instruction, an displaying the information about the client computing devices that are not protected with a backup in a third graphical user interface different from the second graphical user interface.

In a further embodiment of the method, the method includes displaying a second graphical user interface that includes at least one client section corresponding to a client computing device, where the at least one client section is displayed based on the client computing device not being protected with a corresponding backup, and receiving a third instruction using the second graphical user interface to perform a diagnostic on the client computing device to resolve an issue with the client computing device not being protected with the corresponding backup. The method may also include communicating the third instruction to the storage manager to perform the diagnostic on the client computing device, receiving a result of the diagnostic performed on the client computing device from the storage manager based on the communicated third instruction, and displaying the result of the diagnostic on the second graphical user interface.

In yet another embodiment of the method, the method includes displaying a second graphical user interface that includes at least one job status section, wherein the at least one job status section displays job status information for a corresponding backup job established in the information management system, and the job status information includes at least a job identification number, an execution status of the backup job, and an operation type indicating a backup job type of the backup job.

In yet a further embodiment of the method, the method includes displaying a plurality of selectable elements for interacting with a plurality of job status sections displayed in the second graphical user interface, wherein at least one selectable element of the plurality of selectable elements corresponds to an instruction to suspend one or more backup jobs corresponding to the plurality of job status sections, and receiving a selection of the at least one selectable element to suspend the one or more backup jobs. The method may also include communicating a third instruction to the storage manager to suspend the one or more backup jobs based on the received selection, receiving a message from the storage manager indicating whether the suspension of the one or more backup jobs was successful, and displaying a prompt corresponding to the suspension of the one or more backup jobs on the second graphical user interface based on the received message.

In another embodiment of the method, the method includes displaying a job filter overlay overlaid the second graphical user interface, wherein the job filter overlay includes a plurality of selectable options that allow the user to filter backup jobs from the second graphical user interface based on a status of the backup job, receiving a selection of a selectable option corresponding to a particular status, and updating the second graphical user interface to display only those job status sections from the plurality of job status sections that match the selected selectable option.

In a further embodiment of the method, a plurality of search results is received in response to the transmitted first instruction, each search result of the plurality of search results corresponds to a particular entity type, and each search result is displayed on the first graphical user interface in a search result group corresponding to the particular entity type of the search result such that search results of different entity types are not displayed into a same search result group.

This disclosure also describes a non-transitory, computer-readable medium having computer-executable instructions stored thereon that, when executed by one or more processors, cause a system to perform a method comprising displaying a first graphical user interface on a mobile computing device, wherein the first graphical user interface comprises a plurality of elements, including a search query input element configured to receive a search query, and a quick search section, wherein the quick search section displays at least one quick search option for conducting a search within the information management system, and the at least one quick search option corresponds to an entity type of an entity within the information management system. The first graphical user interface may also display a recent search section, wherein the recent search section displays at least one previously submitted search query used to conduct a search within the information management system. The method may further include receiving a search query from at least one of an input into the search query input element, a selection of the at least one quick search option, or the at least one previously submitted search query, transmitting a first instruction to a storage manager in communication with the mobile computing device to perform a search within the information management system using the received search query, and receiving at least one search result from the storage manager in response to the transmitted first instruction.

The method may also include displaying the at least one search result on the first graphical user interface, receiving a second instruction for the at least one search result to perform an operation, communicating the second instruction to the storage manager, wherein the storage manager is configured to communicate the second instruction to the at least one search result to perform the operation.

In another embodiment of the non-transitory, computer-readable medium, the method further comprises displaying a second graphical user interface, wherein the second graphical user interface comprises an overview section associated with the information management system, wherein the overview section displays a graphic indicating a protection status of client computing devices within the information management system, and at least one secondary storage section associated with a secondary storage device, wherein the at least one secondary storage section includes storage status information for the secondary storage device. The method may also include receiving a third instruction using the second graphical user interface to display information about client computing devices that are not protected with a backup in the information management system, and communicating the third instruction to the storage manager to obtain the information about the client computing devices that are not protected with a backup. The method may further include receiving the information about the client computing devices that are not protected with a backup in response to the third instruction, and displaying the information about the client computing devices that are not protected with a backup in a third graphical user interface different from the second graphical user interface.

In a further embodiment of the non-transitory, computer-readable medium of claim, the method includes displaying a second graphical user interface that includes at least one client section corresponding to a client computing device, where the at least one client section is displayed based on the client computing device not being protected with a corresponding backup, receiving a third instruction using the second graphical user interface to perform a diagnostic on the client computing device to resolve an issue with the client computing device not being protected with the corresponding backup, and communicating the third instruction to the storage manager to perform the diagnostic on the client computing device. The method may also include receiving a result of the diagnostic performed on the client computing device from the storage manager based on the communicated third instruction, and displaying the result of the diagnostic on the second graphical user interface.

In yet another embodiment of the non-transitory, computer-readable medium, the method further comprises displaying a second graphical user interface that includes at least one job status section, wherein the at least one job status section displays job status information for a corresponding backup job established in the information management system, and the job status information includes at least a job identification number, an execution status of the backup job, and an operation type indicating a backup job type of the backup job.

In yet a further embodiment of the non-transitory, computer-readable medium, the method further comprises displaying a plurality of selectable elements for interacting with a plurality of job status sections displayed in the second graphical user interface, wherein at least one selectable element of the plurality of selectable elements corresponds to an instruction to suspend one or more backup jobs corresponding to the plurality of job status sections, and receiving a selection of the at least one selectable element to suspend the one or more backup jobs. The method may also include communicating a third instruction to the storage manager to suspend the one or more backup jobs based on the received selection, receiving a message from the storage manager indicating whether the suspension of the one or more backup jobs was successful, and displaying a prompt corresponding to the suspension of the one or more backup jobs on the second graphical user interface based on the received message.

In another embodiment of the non-transitory, computer-readable medium, the method includes displaying a job filter overlay overlaid the second graphical user interface, wherein the job filter overlay includes a plurality of selectable options that allow the user to filter backup jobs from the second graphical user interface based on a status of the backup job, receiving a selection of a selectable option corresponding to a particular status, and updating the second graphical user interface to display only those job status sections from the plurality of job status sections that match the selected selectable option. In other embodiments according to the present invention, a system or systems operates according to one or more of the methods and/or computer-readable media recited in the preceding paragraphs. In yet other embodiments, a method or methods operates according to one or more of the systems and/or computer-readable media recited in the preceding paragraphs. In yet more embodiments, a non-transitory computer-readable medium or media causes one or more computing devices having one or more processors and computer-readable memory to operate according to one or more of the systems and/or methods recited in the preceding paragraphs.

Terminology

Conditional language, such as, among others, “can,” “could,” “might,” or “may,” unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or steps. Thus, such conditional language is not generally intended to imply that features, elements and/or steps are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without user input or prompting, whether these features, elements and/or steps are included or are to be performed in any particular embodiment.

Unless the context clearly requires otherwise, throughout the description and the claims, the words “comprise,” “comprising,” and the like are to be construed in an inclusive sense, as opposed to an exclusive or exhaustive sense, i.e., in the sense of “including, but not limited to.” As used herein, the terms “connected,” “coupled,” or any variant thereof means any connection or coupling, either direct or indirect, between two or more elements; the coupling or connection between the elements can be physical, logical, or a combination thereof. Additionally, the words “herein,” “above,” “below,” and words of similar import, when used in this application, refer to this application as a whole and not to any particular portions of this application. Where the context permits, words using the singular or plural number may also include the plural or singular number respectively. The word “or” in reference to a list of two or more items, covers all of the following interpretations of the word: any one of the items in the list, all of the items in the list, and any combination of the items in the list. Likewise, the term “and/or” in reference to a list of two or more items, covers all of the following interpretations of the word: any one of the items in the list, all of the items in the list, and any combination of the items in the list.

In some embodiments, certain operations, acts, events, or functions of any of the algorithms described herein can be performed in a different sequence, can be added, merged, or left out altogether (e.g., not all are necessary for the practice of the algorithms). In certain embodiments, operations, acts, functions, or events can be performed concurrently, e.g., through multi-threaded processing, interrupt processing, or multiple processors or processor cores or on other parallel architectures, rather than sequentially.

Systems and modules described herein may comprise software, firmware, hardware, or any combination(s) of software, firmware, or hardware suitable for the purposes described. Software and other modules may reside and execute on servers, workstations, personal computers, computerized tablets, PDAs, and other computing devices suitable for the purposes described herein. Software and other modules may be accessible via local computer memory, via a network, via a browser, or via other means suitable for the purposes described herein. Data structures described herein may comprise computer files, variables, programming arrays, programming structures, or any electronic information storage schemes or methods, or any combinations thereof, suitable for the purposes described herein. User interface elements described herein may comprise elements from graphical user interfaces, interactive voice response, command line interfaces, and other suitable interfaces.

Further, processing of the various components of the illustrated systems can be distributed across multiple machines, networks, and other computing resources. Two or more components of a system can be combined into fewer components. Various components of the illustrated systems can be implemented in one or more virtual machines, rather than in dedicated computer hardware systems and/or computing devices. Likewise, the data repositories shown can represent physical and/or logical data storage, including, e.g., storage area networks or other distributed storage systems. Moreover, in some embodiments the connections between the components shown represent possible paths of data flow, rather than actual connections between hardware. While some examples of possible connections are shown, any of the subset of the components shown can communicate with any other subset of components in various implementations.

Embodiments are also described above with reference to flow chart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products. Each block of the flow chart illustrations and/or block diagrams, and combinations of blocks in the flow chart illustrations and/or block diagrams, may be implemented by computer program instructions. Such instructions may be provided to a processor of a general purpose computer, special purpose computer, specially-equipped computer (e.g., comprising a high-performance database server, a graphics subsystem, etc.) or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor(s) of the computer or other programmable data processing apparatus, create means for implementing the acts specified in the flow chart and/or block diagram block or blocks. These computer program instructions may also be stored in a non-transitory computer-readable memory that can direct a computer or other programmable data processing apparatus to operate in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the acts specified in the flow chart and/or block diagram block or blocks. The computer program instructions may also be loaded to a computing device or other programmable data processing apparatus to cause operations to be performed on the computing device or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computing device or other programmable apparatus provide steps for implementing the acts specified in the flow chart and/or block diagram block or blocks.

Any patents and applications and other references noted above, including any that may be listed in accompanying filing papers, are incorporated herein by reference. Aspects of the invention can be modified, if necessary, to employ the systems, functions, and concepts of the various references described above to provide yet further implementations of the invention. These and other changes can be made to the invention in light of the above Detailed Description. While the above description describes certain examples of the invention, and describes the best mode contemplated, no matter how detailed the above appears in text, the invention can be practiced in many ways. Details of the system may vary considerably in its specific implementation, while still being encompassed by the invention disclosed herein. As noted above, particular terminology used when describing certain features or aspects of the invention should not be taken to imply that the terminology is being redefined herein to be restricted to any specific characteristics, features, or aspects of the invention with which that terminology is associated. In general, the terms used in the following claims should not be construed to limit the invention to the specific examples disclosed in the specification, unless the above Detailed Description section explicitly defines such terms. Accordingly, the actual scope of the invention encompasses not only the disclosed examples, but also all equivalent ways of practicing or implementing the invention under the claims.

To reduce the number of claims, certain aspects of the invention are presented below in certain claim forms, but the applicant contemplates other aspects of the invention in any number of claim forms. For example, while only one aspect of the invention is recited as a means-plus-function claim under 35 U.S.C sec. 112(f) (AIA), other aspects may likewise be embodied as a means-plus-function claim, or in other forms, such as being embodied in a computer-readable medium. Any claims intended to be treated under 35 U.S.C. § 112(f) will begin with the words “means for,” but use of the term “for” in any other context is not intended to invoke treatment under 35 U.S.C. § 112(f). Accordingly, the applicant reserves the right to pursue additional claims after filing this application, in either this application or in a continuing application. 

We claim:
 1. A system for managing and configuring operations of an information management system, the system comprising: one or more processors that, having executed computer-executable instructions, configure a mobile computing device to perform a plurality of operations comprising: displaying a first graphical user interface at the mobile computing device, wherein the first graphical user interface comprises a plurality of elements, including: a search query input element configured to receive a search query related to operations of the information management system; receiving a search query; transmitting the received search query to the information management system; receiving at least one search result from in response to the transmitted search query; displaying the at least one search result; receiving a first user selection related to the at least one search result; in response to the first user selection, displaying a second graphical user interface that includes at least one job status section, wherein the at least one job status section displays job status information for an information management job, and the job status information comprises at least a job identifier associated with the information management job, a status associated with the information management job, and an operation type indicating a job type of the information management job, wherein the second graphical user interface is different from the first graphical user interface; in response to receiving the first user selection, displaying a plurality of selectable elements, wherein at least one selectable element of the plurality of selectable elements indicates an instruction for the information management system associated with at least one or more information management jobs; receiving a second user selection for one or more selectable elements of the plurality of selectable elements; and communicating to the information management system, at least one instruction corresponding to the second user selection, wherein the information management system performs at least one operation associated with the at least one instruction.
 2. The system of claim 1, wherein the first graphical user interface further comprises: a quick search section that displays at least one quick search option for conducting a search within the information management system, and the at least one quick search option reflects an entity type of an entity within the information management system.
 3. The system of claim 2, wherein the receiving of the search query further comprises receiving a quick search selection of the at least one quick search option.
 4. The system of claim 1, wherein the first graphical user interface further comprises: a recent search section that displays at least one previously submitted search query used to conduct a search within the information management system.
 5. The system of claim 4, wherein the receiving of the search query further comprises receiving a recent search selection of the least one previously submitted search query.
 6. The system of claim 1, wherein the information management system comprises a plurality of computing modules for managing data protection operations within the information management system.
 7. The system of claim 1, wherein the plurality of operations further comprises: displaying a third graphical user interface, wherein the third graphical user interface comprises: an overview section associated with the information management system, wherein the overview section displays a graphic indicating a protection status of client computing devices within the information management system; and at least one secondary storage section associated with a secondary storage device, wherein the at least one secondary storage section includes storage status information for the secondary storage device; receiving a third instruction using the third graphical user interface to display information about client computing devices that are not protected with a backup in the information management system; communicating the third instruction to the information management system to obtain the information about the client computing devices that are not protected with a backup; receiving the information about the client computing devices that are not protected with a backup in response to the third instruction; and displaying the information about the client computing devices that are not protected with a backup.
 8. The system of claim 1, wherein the plurality of operations further comprises: displaying a third graphical user interface that includes at least one client section corresponding to a client computing device, where the at least one client section is displayed based on the client computing device not being protected with a corresponding backup; receiving a third instruction using the third graphical user interface to perform a diagnostic on the client computing device to resolve an issue with the client computing device not being protected with the corresponding backup; communicating the third instruction to the information management system to perform the diagnostic on the client computing device; receiving a result of the diagnostic performed on the client computing device from the information management system in response to the communicated third instruction; and displaying the result of the diagnostic on the mobile computing device.
 9. The system of claim 1, wherein the plurality of operations further comprises: displaying a job filter overlay overlaid the second graphical user interface, wherein the job filter overlay includes a plurality of selectable options that allow the user to filter the information management jobs from the second graphical user interface based on a status of the information management job; receiving a selection of a selectable option corresponding to a particular status; and updating the second graphical user interface to display only those job status sections from the plurality of job status sections that match the selected selectable option.
 10. The system of claim 1, wherein each search result of the at least one search results corresponds to a particular entity type.
 11. A method for managing and configuring operations of an information management system, the method comprising: displaying a first graphical user interface at a mobile computing device, wherein the first graphical user interface comprises a plurality of elements, including: a search query input element configured to receive a search query related to operations of the information management system; receiving a search query; transmitting the received search query to the information management system; receiving at least one search result from in response to the transmitted search query; displaying the at least one search result; receiving a first user selection related to the at least one search result; in response to the first user selection, displaying a second graphical user interface that includes at least one job status section, wherein the at least one job status section displays job status information for an information management job, and the job status information comprises at least a job identifier associated with the information management job, a status associated with the information management job, and an operation type indicating a job type of the information management job, wherein the second graphical user interface is different from the first graphical user interface; in response to receiving the first user selection, displaying a plurality of selectable elements, wherein at least one selectable element of the plurality of selectable elements indicates an instruction for the information management system associated with at least one or more information management jobs; receiving a second user selection for one or more selectable elements of the plurality of selectable elements; and communicating to the information management system, at least one instruction corresponding to the second user selection, wherein the information management system performs at least one operation associated with the at least one instruction.
 12. The method of claim 11, wherein the first graphical user interface further comprises: a quick search section that displays at least one quick search option for conducting a search within the information management system, and the at least one quick search option reflects an entity type of an entity within the information management system.
 13. The method of claim 12, wherein the receiving of the search query further comprises receiving a quick search selection of the at least one quick search option.
 14. The method of claim 11, wherein the first graphical user interface further comprises: a recent search section that displays at least one previously submitted search query used to conduct a search within the information management system.
 15. The method of claim 14, wherein the receiving of the search query further comprises receiving a recent search selection of the least one previously submitted search query.
 16. The method of claim 11, wherein the information management system comprises a plurality of computing modules for managing data protection operations within the information management system.
 17. The method of claim 11, wherein the method further comprises: displaying a third graphical user interface, wherein the third graphical user interface comprises: an overview section associated with the information management system, wherein the overview section displays a graphic indicating a protection status of client computing devices within the information management system; and at least one secondary storage section associated with a secondary storage device, wherein the at least one secondary storage section includes storage status information for the secondary storage device; receiving a third instruction using the third graphical user interface to display information about client computing devices that are not protected with a backup in the information management system; communicating the third instruction to the information management system to obtain the information about the client computing devices that are not protected with a backup; receiving the information about the client computing devices that are not protected with a backup in response to the third instruction; and displaying the information about the client computing devices that are not protected with a backup.
 18. The method of claim 11, wherein the method further comprises: displaying a third graphical user interface that includes at least one client section corresponding to a client computing device, where the at least one client section is displayed based on the client computing device not being protected with a corresponding backup; receiving a third instruction using the third graphical user interface to perform a diagnostic on the client computing device to resolve an issue with the client computing device not being protected with the corresponding backup; communicating the third instruction to the information management system to perform the diagnostic on the client computing device; receiving a result of the diagnostic performed on the client computing device from the information management system in response to the communicated third instruction; and displaying the result of the diagnostic on the mobile computing device.
 19. The method of claim 11, wherein the method further comprises: displaying a job filter overlay overlaid the second graphical user interface, wherein the job filter overlay includes a plurality of selectable options that allow the user to filter the information management jobs from the second graphical user interface based on a status of the information management job; receiving a selection of a selectable option corresponding to a particular status; and updating the second graphical user interface to display only those job status sections from the plurality of job status sections that match the selected selectable option.
 20. The method of claim 11, wherein each search result of the at least one search results corresponds to a particular entity type. 